[Xerte] Re: language
Julian Tenney
Julian.Tenney at nottingham.ac.uk
Wed Jan 13 11:41:15 GMT 2016
Ah, OK. cheers!
Elly let us know if that doesn’t work
From: xerte-bounces at lists.nottingham.ac.uk [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Fay Cross
Sent: 13 January 2016 11:40
To: Xerte discussion list
Subject: [Xerte] Re: language
If Elly creates the page again like Inge suggests then the strings should all be in Dutch (and appear in the editor’s language options so they can be edited anyway if needed)
From: xerte-bounces at lists.nottingham.ac.uk<mailto:xerte-bounces at lists.nottingham.ac.uk> [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Julian Tenney
Sent: 13 January 2016 11:38
To: Xerte discussion list
Subject: [Xerte] Re: language
What needs to happen in Elly’s case then Fay?
From: xerte-bounces at lists.nottingham.ac.uk<mailto:xerte-bounces at lists.nottingham.ac.uk> [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Fay Cross
Sent: 13 January 2016 11:37
To: Xerte discussion list
Subject: [Xerte] Re: language
They’re not completely hard coded. It looks for the strings in the xwd but if it doesn’t find them then uses strings hard coded in the page model as a fall back. I guess this project must have been made before those language strings were in the xwd but I’m not sure of the best way to do this to avoid ever having fall backs in the model files.
There are probably quite a lot of pages with similar issues as if new features have been added then there are often strings associated with them. If you then add the new feature to an older page then it will always use the hard coded string. The only way around this I can think of is that where people notice this is a problem they need to create the page from scratch again.
From: xerte-bounces at lists.nottingham.ac.uk<mailto:xerte-bounces at lists.nottingham.ac.uk> [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Julian Tenney
Sent: 13 January 2016 11:26
To: Xerte discussion list
Subject: [Xerte] Re: language
The feedback strings are hardcoded in the mcq.html file: must have missed those:
Two options: either use the Language Options checkbox and change the values, but you’ll have to do it each time; or if you have access to the server change mcq.html lines 108 – 123 to the strings you want.
I’ll log it as a bug and we’ll fix it at some point,
Thanks,
From: xerte-bounces at lists.nottingham.ac.uk<mailto:xerte-bounces at lists.nottingham.ac.uk> [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Elly Langewis
Sent: 13 January 2016 11:15
To: Xerte discussion list
Subject: [Xerte] language
Hi all,
Is it true that no matter what the language is set on the learning object level, feedback to MC questions will always end with an English sentence, like "Your answer was incorrect."?
Even in the example in Dutch which was given by Inge Donkervoort this is the case (see attachment).
I hope this is not true...
Elly
Elly Langewis, CPIO
eLearning, eLectures & eAssessment
Department of Biology
Utrecht University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte/attachments/20160113/b893296b/attachment-0001.html>
More information about the Xerte
mailing list