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"?
Is the translation done locally in the specific country? If so, the font will adopt that country's equivalent of Trebuchet MS, i.e. Trebuchet MS CE because it is being used on that country's computer. I believe the CE is for Central Europe?
The workaround that I use is to highlight the translated column, then change the font back to the original font type, i.e. Trebuchet MS.
I found that Open Sans is not translated correctly in some European languages, so when the word doc is returned to me, I highlight and change the translated column toArial.
yes the Translation was done localy in the courntry, but the font type in the word document is correct. The fonttype is changed when reimporting the translation into the Storyline file.
The font type doesn't change after reimporting. It appears correctly in the Word doc but it is actually retaining the font from the country computer and this is why it appears to change when you reimport it. It is still the same font (even though it has CE) and there is no need to change it in Storyline.
If you're still having difficulty with this, we'll want to take a look at your .story file and the translated Word document and determine what happens on our end as well. You'll also want to confirm that you're working on local project files as working off a network drive is known to cause issues.
If you want to share your file you can upload here using the "Add Attachment" button and you're also welcome to send along to our Support Engineers.
thank you for your offer to support me. Is there any possibility to provide you the documents in a more private way? I don't want to publish the course for everybody.
Thanks Stefanie, and it looks like Abel is working on your case (# 00811392 for my reference) so I'll continue to follow along as we tests your set up.
I checked on your case and it seems that Abel was already able to replicate it and he reported it to our QA team for additional review. It seems that it's specific to Czech language and some words or phrases. We'll keep you posted as a part of your case with any updates or information.
Thanks for sharing one of the threads you took a peek at. That one is a bit dated and I searched for a support case for the user and looks like it was not shared, so I have no update to provide on that issue.
You are welcome to share your examples with the support team here so that we can take a look and share with the QA Team as well if needed.
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.
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!
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.
29 Replies
Hi Stefanie
Is the translation done locally in the specific country? If so, the font will adopt that country's equivalent of Trebuchet MS, i.e. Trebuchet MS CE because it is being used on that country's computer. I believe the CE is for Central Europe?
The workaround that I use is to highlight the translated column, then change the font back to the original font type, i.e. Trebuchet MS.
I found that Open Sans is not translated correctly in some European languages, so when the word doc is returned to me, I highlight and change the translated column toArial.
Hope this is helpful.
Hi,
yes the Translation was done localy in the courntry, but the font type in the word document is correct. The fonttype is changed when reimporting the translation into the Storyline file.
Hi Stephanie
The font type doesn't change after reimporting. It appears correctly in the Word doc but it is actually retaining the font from the country computer and this is why it appears to change when you reimport it. It is still the same font (even though it has CE) and there is no need to change it in Storyline.
Hi Stefanie,
If you're still having difficulty with this, we'll want to take a look at your .story file and the translated Word document and determine what happens on our end as well. You'll also want to confirm that you're working on local project files as working off a network drive is known to cause issues.
If you want to share your file you can upload here using the "Add Attachment" button and you're also welcome to send along to our Support Engineers.
Hi Ashley,
thank you for your offer to support me. Is there any possibility to provide you the documents in a more private way? I don't want to publish the course for everybody.
Hi Stefanie
here is the link for private support
I've already send the files with the link "along to our Support Engineers" this morning. I hope you can help me.
Thanks Stefanie, and it looks like Abel is working on your case (# 00811392 for my reference) so I'll continue to follow along as we tests your set up.
Hi Stefanie,
I checked on your case and it seems that Abel was already able to replicate it and he reported it to our QA team for additional review. It seems that it's specific to Czech language and some words or phrases. We'll keep you posted as a part of your case with any updates or information.
Hi Ashley Terwilliger,
I've encountered the same issue. Is there any solution?
Why does this kind of issue happen in .story?
Hi Eunsil!
The issue shared in this thread was specific to the Czech language. Does that fit the issue you are seeing as well?
Hi Leslie McKerchie,
I have also this issue in other languages, including Czech.
You can find this kind of issue in this Discuss section.
Please access the link below.
https://community.articulate.com/discussions/articulate-storyline/help-font-changes-when-importing-russian-translation
Please help me. :)
Hi Eunsil!
Thanks for sharing one of the threads you took a peek at. That one is a bit dated and I searched for a support case for the user and looks like it was not shared, so I have no update to provide on that issue.
You are welcome to share your examples with the support team here so that we can take a look and share with the QA Team as well if needed.
Hi Leslie,
Please check the link below as well.
https://community.articulate.com/discussions/articulate-storyline/arial-unicode-ms-in-translated-documents
https://community.articulate.com/discussions/articulate-storyline/translation-font-change
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:
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.