Urgent please: Diacritic signs problems when publishing to SCORM


I am currently working on a big project for french speaking customers. 

I have a problem with diacritic marks such as accent etc. with interaction reports from SCORM published courses.

They display correctly in Soryline quiz questions as well sa review slides but do not appear in interaction reports in Docebo. The same problem appears in SCORM Cloud log files.

What is very strange is that they are OK in the question text (description) in both Docebo and SCORM Cloud, but they do not display in the choice of answers and the user answer.

Here joined screen copy of SL question, SL review slide, Docebo interaction report and full SCORM debug log. (see question 8 highlighted on 3rd page)

This is really critical since my french speaking customer cannot accept the project with these errors.


7 Replies
Ashley Terwilliger-Pollard

Hi Dominique, 

You may find that non-English characters in question and answer text are replaced by underscores (_) in LMS debug logs or reports.

We replace non-English characters with underscores when communicating with an LMS to conform to AICC and SCORM 1.2 standards. These specs only support letters, numbers, and a few special characters (!, $, %, *, etc.). SCORM 2004 supports more characters, but many LMSs don't. Sending unexpected characters could cause LMS reporting to fail. 

This is not considered a bug, as it's a setting and requirement of the SCORM outputs. 

Dominique D

Hi Ashley,

I am not sure to totally agree. First by replacing replacing some characters with _ although SCORM 2004 supports them, you do not fully comply to the standard. Second, why impose limitations due to a standard SCORM 1.2 which is still well supported, but pretty old. Third why would you have to limit yourself because some LMS do not comply to standards!

Finally and most importantly, you assumption is not correct, because the characters perfectly appear and are supported all the way (I mean in SCORM Cloud, Docebo etc) in the question title (description) where you do not replace them with _.  You can check that by having a closer look at the SCORM Cloud debug log and Docebo screen capture.

As for what is supported or not by SCORM 2004 standard our team is further checking it.

Thanks for reading.

Dominique D

Hi again,


It appears that the character restrictions  in SCORM 2014 do apply  to the Interaction ID. However they do not apply to Interaction Description, Interaction correct_response and Interaction Learner_response. It is however the reason why diacritics that you DO NO replace with _ in the Interaction Description do not make any problem and go all the way... through SCORM Cloud, Docebo and others, as they would most probably go all the way through in Interaction correct_response and learner response.

Tanks again

Ashley Terwilliger-Pollard

Hi Dominique, 

I'm not sure I'm clear on your most recent reply - but the above information I shared is what we received from our QA team after their investigation into if it was a bug - and one of the resources they utilized was the information documented by Rustici here. Hope that helps 

Dominique D

Hi Ashley,

It does make sense in some way, but the real problem comes from the fact that in Multiple Choice Interactions SL  sends the choice text as in the question Form view instead of sending the Multiple Choice radio button ID as specified in the Timeline Slide view although this could also make some problems, but less likely.

Anyway, by sending the choice text a greek user will receive a string full of _ as the learner response which is not an option.

SCORM 2004 indeed requires that the valid answers as well as learner answer be IDs and not localized text. Unfortunately the only question type which accepts localized strings as correct_answer and learner_answer is the fill in the blank.

This means that the instructor will have to rely on the answer ID or answer number only in the reports. :-(



Ashley Terwilliger-Pollard

Hi Dominique, 

I don't see mention of Tin Can in the QA report that I reviewed to determine this answer, but it's easy enough to test Tin Can content at SCORM Cloud as well. You may see this error message when uploading there, but it can safely be ignored.  If you have a few slides handy with the accented characters I'm happy to take a look too - and that'll be a bit faster than finding how to add those characters myself with symbols. ;-)