Should I save imsmanifest.xml in UTF-8 or ANSI ?
ADL test suite 1.2 seem to fail with UTF8 header, but on otherhand some LMSes will fail if its not UTF8.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Should I save imsmanifest.xml in UTF-8 or ANSI ?
ADL test suite 1.2 seem to fail with UTF8 header, but on otherhand some LMSes will fail if its not UTF8.
UberAlex is correct. SCORM leaves it up to the XML parser. SCORM merely says that it needs to be valid XML. If you are getting errors with XML parsers, make sure that the tool you are using to edit and save your manifest actually encodes the document using the same encoding that you specify. If you specify that the document is UTF-8, but the editor saves it as ASCII you can run into problems.
Also of note, in the run-time portion of SCORM, the characters are encoded as ISO 10646 (or, unicode. Since some data in the manifest can feed in to the run-time, ensure that your strings will be compatible with ISO 10646.
Also, make sure that any URLs, file paths and parameter strings are properly encoded for HTTP use.