Arial Unicode MS in translated documents

Further to the above, I have noticed that the fonts in Word appear with the icon for Open Type fonts but when viewed in SL2 they have the icon for True Type fonts (on the same PC).

Hi Sarah!

I'm not seeing this behavior in my testing.

I created text with Arial Unicode MS, exported the translation which had the same text (new typing wanted Calibri), and imported just like shown in Word.

Does this happen in all of your files?

Hi Leslie

The test I have just run was to create a slide with the following text in Arial Unicode MS:

Message to test how Arial Unicode MS text is imported into Storyline.

I exported the Translation and then used Google Translate to translate it into Spanish:

Mensaje para probar cómo el texto Arial Unicode MS se importa en historia.

I pasted the Spanish translation in place of the English in the Word file, being sure to maintain the format (ie. Arial Unicode MS).

When I then imported this translation back into my Storyline slide the text came in as Arial Unicode MS Western.

I should add that this only happens when there are accented characters within the translated text.

Finally, I changed the Spanish text in the word file to Arial and imported it again. When Arial font is used the text remains Arial when imported again (but, unfortunately, my customer wants Arial Unicode MS).

The font with "Western" at the end does not display correctly and it doesn't happen to strings with no accented characters so it leaves the job looking a mess. My only solution is to re-apply the correct font after the translation has been imported but this is time-consuming for a course that is translated into 20 different languages.

Unfortunately, I am not able to download your attachment or upload my test file :-(

Hi Sarah,

What's happening when you're trying upload or download the attachment? Are you just unable to share her publicly? You could reach out to our Support Engineers here if you'd like to share privately. 

Hi. The issue with the attachments is company security block. I have created a sample file which shows the issue and sent it to the Support Engineers. Hopefully, it will get resolved soon.

Thanks for the update Sarah. Looks like your support case (00881390) made it through and you should be hearing from someone soon. I'll follow along as well.

Hi Sarah! 

I popped in to check on your case and it looks like our team was able to duplicate and they have shared this information with our QA Team. 

The workaround, for anyone following along, is to manually change the font to your preferred style if the font is not correct after importing the word file for translation. 

Hi Leslie

Thank you for the update.

We have also done some more testing here and have found that if we export the content for translation as XLIFF, when we import the translated text again (from XLIFF) it comes in with the font correct. So it seems this issue is related to the way the Word file is imported.

We are now looking into a process with XLIFF output but it is not ideal to me as I am not able to see the output before it goes off to our translators. We also need to make sure is that the caption label changes from "new" to "translated" in the XLIFF file to enable us to import the text - for the test it didn't work the first time and we changed it manually, but this would not be feasible for a large project.

I have fed this result back to the Customer Support Engineer but still really keen to get a solution for the issue when using the Word interchange process.

Sarah, thanks so much for popping back in with that additional information-- helpful for sure.  Once we have some additional insight to share, we'll do so right here, as well.

Hi Folks - does Articulate have an update on this issue?

I'm working in Storyline 3.9.21069.0 (Update 9) and I'm seeing the exact same behavior.

Similarly, using Polish text, Storyline somehow changes Arial Unicode MS to Arial Unicode  MS CE.

It seems to change Calibri to Calibri CE.

With French it is Arial Unicode MS Western.

I don't think any of these are actual fonts - there are no fonts by that name on my system, nor appearing in any Font Menus. It appears to be some fragmented Character Set reference - which should be unnecessary for a Unicode font. All of the Character Sets are included by definition in the Unicode font set. One can view these Character Sets using the Character Map Utility that comes with Windows OS.

I currently have an open Case with support on this issue, and have tried to cite this thread, with little success. They are so far unable to reproduce this (somehow). I have confirmed this occurs for colleagues, etc., so that explanation isn't working for me.

 Thanks for any updated information.

I have uploaded a pic showing that there is no separate font named with Western, nor CE, but rather, these are simply Character Sets within the Unicode Font named: Arial Unicode MS. i.e. There are no actual fonts named Arial Unicode MS Western, nor Arial Unicode MS CE.

I have also uploaded a pic showing Storyline in a state where the Font Menu displays Arial Unicode MS CE, even though no such font exists on WIndows (or in reality.

Are Leslie or Crystal still around by any chance?

Hi Adam!

I see that you're working in a support case with one of our Support Engineers, Lianne! Great call!

I encourage you to continue troubleshooting with Lianne so that we can find a fix. Please let me know if you have any questions!

Hi Lauren, I see there has been another Storyline update.

Support confirmed the issue, but there has been no update.

Is there any way to find out what kind of priority this has been given?

It sure looks like a problem that is at least 3 yrs. old and counting...

Regards,

- Adam