Forum Discussion
Fonttype is changed after importing a Word translation file
Hello,
I've made a translation using the Storyline Word translation export with reference column. The translation export worked fine, but when I import the translation again the font type is changed. In the Word file the whole text is in "Trebuchet MS" and after the import it seems to be "Trebuchet MS CE", a fonttype which is not even installed on my pc. So in reality I think it's displayed in "Arial".
Does anybody know why the text is not displayed in "Trebuchet MS"?
29 Replies
Hi Eunsil!
I see that you reached out to our support team (00895215) and that Robert was able to assist you with some text not displaying.
The links that you are sharing with me lead me to believe that you were having an issue with the font upon import.
Feel free to respond by to Robert in your case if you need further assistance.
This issue is still present in Storyline 2 build 1609.3020. It's a really big problem for us.
I created a test project with a single screen and one text box using the Cambria font. I exported to Word DOC, translated the text into Russian, then imported the Russian DOC. Storyline appends " Cyr" to the font name, even though the Cambria font supports Cyrillic characters. Because "Cambria Cyr" is not a valid font name, a different font gets picked randomly.
It's really weird, as Stroyline guesses the language script based on the characters in the string, and then bizarrely appends Cry for Russian, CE for Eastern European and TR for Turkish language text. This breaks the formatting for all that text.
We have very large courses, and this causes us to perform hours of manual changing of fonts every time we import translations.
I attached my test files to reproduce the issue.
Beat Stauber
PTIGlobal
Interestingly this issue does not happen if the font in the source story file is set to Arial. I think there is some really strange source code behind this font selection "feature". Better sort this out if you are serious about translation support in Storyline.
Hi Beat. Thanks so much for taking the time to write up your findings and to include your example files. I've added that detail to our report of this issue, so we are going to continue investigating with our team to see if we can improve the translation feature for those languages. I know that must be pretty frustrating to have to redo those fonts that are not importing correctly.
Hopefully we will be able to make some progress here!
We found a workaround for this that's much faster than manually applying the correct font to all controls:
- Rename the story file to .zip and unizp the file.
- Search for all occurrences of the bad font names, e.g. "Cambria Cyr". They should be mostly in the slide XML files.
- Replace all occurrences with the correct font name "Cambria".
- Zip up the project and rename to .story
- Open the story file and make sure everything looks good.
- Have a cup of coffee. :-)
Cheers,
Beat Stauber, Senior Localization Engineer @ PTIGlobal
Thanks for popping in to share your findings and solution Beat. On this Monday morning, the cup of coffee is the best part :)
Please be aware that this ugly bug happens in the latest version of Storyline 360 as well. Any chance it will get fixed?
Hello Beat - Thanks for letting us know that this happens in SL360 as well. I will get this reported to our team as well. I was able to use the same files you included here earlier, so thank you.
When updating a story from AS2 to AS3 I get the same issue. Sollution from PTI Global works like a charm, but it is still very annoying.
Hi Suzanna and welcome to E-Learning Heroes :)
Sorry to hear that you've run into an issue as well, but glad that the tips shared here will help you out.
Curious if you are using a Czech language/font as well?
Thanks for the advice from PTI Global. With Storyline 360 it is no longer necessary to change the font in the XML files.
With the function Find/Replace > Replace Font we could change the font directly in the project file.
