Accented characters in text entry and fill in the blanks

Aug 12, 2015

I have created some text entry and fill-in-the-blank questions that require accented characters to answer. It is not possible to type accented characters into the box - though you can paste them.  I am using Articulate Storyline 2 (update 1507:2315) which is the latest version.  I am using the standard English version

I understood that this had been fixed in the latest release.

Is there a solution to this problem?

3 Replies
Ashley Terwilliger-Pollard

Hi Niall,

All the release notes for the latest updates and previous ones are detailed here. I am looking to see if there is an associated bug for what you mentioned - but I don't see one. Do you have a keyboard with these characters or are you using something like the Alt GR key to access them? If the latter I've seen folks mention using this method and if the former, I think we'd want to know a bit more about your keyboard language set up and where you're unable to enter the characters (preview/publish/environment/browser).  

I do know 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.

Niall Watts

HI Ashley

Thanks.  I am using AltGr on a UK keyboard to write in Irish Gaelic.  Fortunately, the problem only seems to occur in preview and after a lot of frustrating hours, I published the story and found that  text entry works with á é etc. I am using Firefox and publishing to web so no concerns about SCORM

I interpreted the product support post at  to mean this was no longer a problem

Using the ALT-keypad combination is considered rather klunky these days - takes me back to the 1980s!!!

Anyway problem seems to be resolved


This discussion is closed. You can start a new discussion or contact Articulate Support.