Forum Discussion
SCORM 1.2 Title Tag not in UTF-8
Our team created a course that is in 6 different languages, all through the testing process we ensured that all characters were appearing correctly through each stage.
Now that we are placing them onto our LMS we noticed that the title tag for each scorm pop-up is not set to UTF-8. We dove into this to ensure that it was not our platform that caused this. We can confirm that it is the Scorm file that is missing the UTF-8 information for the title tag and not the platform, the platform does not define what appears in the title tag; the scorm file does.
I have attached screenshots showing the title tags that are appearing for all character-based languages, as well as any languages that have accented letters.
Does anyone know how to fix this?
- RémiACommunity Member
Hi Laurelle,
I had this problem for a while with all our content in french. At first, I was sure that the problem came from the LMS or the server. After testing on ScormCloud : same problem, so apparently this comes from RISE publish. With Storyline, no problem at all.
So it seems the utf-8 charset is missing in the indexAPI.html in scormdriver folder (see the attachment)
Just add <meta charset="utf-8"> before the <title> and let me know if it works
@ArticulateStaff , maybe there's a problem with the publish files?
Hi Remi,
Thanks for helping out! This post will be especially helpful to anyone who goes to ELH looking for help with a similar inquiry.
The inclusion of the metadata character set in the translation file is not yet a standard feature so I went ahead and added this to an open feature request that we have for the ability to set the original source language in translation options. We'll let you know if this feature makes it to our roadmap.
- LaurelleJnoB539Community Member
Hello Jose,
I hope it does make it to the roadmap, we have almost 100 courses in development that are in languages that will require utf-8. Ensuring that each course has the code in the index file is not ideal.
- LaurelleJnoB539Community Member
Thank you for this Remi, it will be a nice interim fix until this is (hopefully) is added to the feature roadmap.