Correct letter-case of text encoding declaration necessary for Moodle

Question

I have never encountered this before now but the letter-case of the text encoding declarations in XML files from the e-Learning online platform Moodle must stay the same or it will fail when you attempt to restore the course.

When XML files are pulled from Moodle, the declarations look like this:

<?xml version="1.0" encoding="UTF-8"?>

Studio changes to this:

<?xml version="1.0" encoding="utf-8"?>

If we don't keep the letter-case identical, then we can't upload the translated package. Is there any way around this? Has this been encountered before and is there talk of a fix for this 'bug'?

Luke Hipsher · Accepted Answer

Hi Paul,

An update on this... The Developer of the client's Moodle course was able to patch the issue on their end so that any lettercase format of the text-encoding declaration is acceptable. If anyone experiences this, please suggest to your client to look into patching the issue on the Moodle-side to accept any lettercase of the text-encoding.

Thanks,
Luke

Paul Filkin · Answer

Hi Luke Hipsher 
 
I've never come across this before and didn't even notice it until you pointed it out. But I can confirm this happens with any XML file. I don't believe it's a bug because there isn't a requirement (as far as I can see) for upper-case encoding only. It seems to be the preferred and all tools should be able to handle uppercase, so that would be a bug if Studio didn't handle uppercase for examp But changing it to lowercase should not break anything according to the standard. 
 
I think there is a good argument for leaving it as it finds it and not changing to lowercase, but I would see this as an enhancement and not a bug fix. 
 
I'll check with the dev team and see what they think. 
 
Thanks 
 
Paul

Paul Filkin · Answer

Hi Luke Hipsher 
 
I discussed this with the development team and their view is that the problem lies with Moodle because it has a problem with case sensitivity where it should really be agnostic. The effort to make this change in Studio would be significant as the change is automatically made by the .NET XML processor so we would have to override this. 
 
So it's no bug, it would be an enhancement, but we are unlikely to be willing to address this. I guess for your purposes it might not be too hard to create a custom batch task to change the case back to uppercase when the target files are created... that might be your best option and could be done by any developer (including the developers LS have access to through the LDTS team )

Trados Studio > 1. Trados Studio

Correct letter-case of text encoding declaration necessary for Moodle