Error (warning) when publishing interactions with non-Western Char
Feb 11, 2013
I am working on a localization project with someone else. We both have the same versions of Studio '09 products ( w/ latest updates applied).
When she publishes an interaction in, for example, Japenese, she has no issues. When I do the same, I get the following warning:
I understand that the interaction title (which is in Japanese) is part of the file path, & hence the warning.
It appears to work correctly, regardless of whenther I'm publishing into the ppt (i.e. publishing for LMS), or publishing for the web.
So, the questions:
1. As long as it looks ok when I view it from my browser, should it also be ok when loading in the LMS (I don't know what LMS the client uses).
2. Any ideas as to why I would get such an error message & someone else would not when we're both working on the same Articulate versions?
Thanks!
-Carol
5 Replies
Hi Carol,
If you will be working with non-western languages in your quizzes, it is recommended that you use a unicode font, such as Arial Unicode MS, in order for your non-western text to appear correctly in your published quizzes.
You can create a reusable quiz template that works with non-western languages in Quizmaker ‘09. Here’s how.
If it's working fine for you now, I wouldn't be too concerned with the error. However, if you leave the course the way it is and you continue to see the error, I'm a little concerned with how the course will appear when it's uploaded to the LMS. Also, keep in mind that if you don't use the suggestion above, you may see some underscores reported to the LMS, as well.
Are you able to upload and test the content on the LMS?
Thanks!
Hi Christine, I have this issue with interactions, not quizzes. However, I did go back & check both (there is a pre-defined Japanese Template). Anyehere I see reference to a font, it is already pre-set to Arial Unicode MS.
I did find that my partner was not publishing her interactions outside of ppt, she just edited them from ppt, saved them back into ppt (or I should say, presenter), and published it all at once. If she published outside of ppt, she did get the same error.
(And likewise, if I get into engage from ppt - then save back to ppt, and later publish the entire presentation - I do not get this error).
HOWEVER - I do run into one issue, even though everything seems to be set to Arial Unicode MS:
The slide properties gets a garbled version of the interaction (or quiz) title when an interaction (or quiz) is inserted into ppt. Not a big deal, I can go & reset that title through slide properties.
The other area I see the garbled interaction (quiz) name is in the list of available interactions (or quizzes) to me when I try to change the properties of an interaction (or quiz) from the ppt. slide. See below:
The actual file names are fine (tabs.intr & tabs2.intr)
In Tabs.intr - i left the 'title' of the interaction as "Tabs", in Tabs2.intr, I changed that to Japenese.
So I concluded it's the title that is causing the problem. The Title font is set to Arial Unicode MS.
I'm at a loss.
Do I need to be concerned, since the only erroneous thing you see inside the course when it runs was the interaction title in the TOC... but that I corrected through slide properties.
Hi Carol,
Sorry about that! This is in the Quizmaker section, but I should've noticed the big "Engage" portion of the first screenshot you posted.
This sounds a little more like a known issue we've found with some languages.
I believe this is what you used to correct the TOC title, right?
If your Engage interaction title contains non-Western characters (such as Chinese, Cyrillic, or Russian), you may find that it does not display correctly when embedded into a Presenter presentation. Please review this article for more information.
oops ... sorry ! thanks for the info though. TOC is corrected & apparently, the other issue isn't rearing it's ugly head in the LMS.
Awesome, glad to hear it! If you run into any issues with this down the line, please let us know!
I hope you have a great evening, Carol
This discussion is closed. You can start a new discussion or contact Articulate Support.