Storyline 360 renaming fonts on import to invalid font names

Nov 06, 2019

Hi all,

I work for a company that translates lots of eLearning.

For about a year now, we've had a problem with Storyline changing the names of fonts on us during translation import.

The best example is a recent one.

We made Word exports from SL. Had them translated. Course font was Georgia. Which supports basically all European languages.

I checked the translated exports in Word and it was just "Georgia"
Upon import, some locations had the font name changed, which broke the formatting and Storyline substituted.

This came up in Turkish, Russian and Polish all had the font name appended to

Georgia Tur

Georgia Cry

Georgia CE

It did not do this for Spanish, French, Italian

It did not do this in every text box, but enough it added significant time to the job that is really not acceptable. This happens for all users on my team (9 people).

We've also seen it, when we've had Japanese->English jobs, and it adds "Western" to the end of font names.

7 Replies

Lauren Connelly
Staff

over 4 years ago11/07/19 at 8:09 pm (UTC)

Hi Matt!

Unfortunately, we've seen this error before and our team has determined this is a bug. I'm going to share your comments with our team, but it would also be helpful to share a file. Would you mind attaching your file to this discussion using the "add attachment" button?

Franz Müller

over 4 years ago01/13/20 at 3:21 pm (UTC)

Hello!

Is there any development progress on this problem? When will the bug be fixed? We have the same problem with our translations into Turkish.

Franz Müller

over 4 years ago01/13/20 at 3:59 pm (UTC)

Please find attached three sample files:

File1: The original file with "Trebuchet MS". In this example the text is already in Turkish.
File2: Here you see the MS Word export. No further changes have been made.
File3: This is the storyline file after importing File2. The font is "Trebuchet MS Tur" and when I close and reopen the file, Storyline tells me that this font is not installed.

Please let me know how long you will need to fix this problem as checking and correcting the text is very time consuming.

Lauren Connelly
Staff

over 4 years ago01/13/20 at 8:56 pm (UTC)

Hi Franz!

I'm passing this information along to my team. I don't have a timeline to share, but I'll report back we have an update.

In the meantime, I found this workaround that seemed to do the trick! Let me know if it works for you!

Franz Müller

over 4 years ago01/24/20 at 1:26 pm (UTC)

Thank you Lauren! This workaround sounds a little bit dangerous to me. For my current project, I find changing the fonts directly in Storyline more appropriate.

Phil Mayor
Hero

over 4 years ago01/24/20 at 1:38 pm (UTC)

You should be able to do a quick replace font on the find and replace menu will take 1 minute

Lauren Connelly
Staff

2 years ago02/23/22 at 6:30 pm (UTC)

Hello everyone!

I wanted to quickly share that we aren't seeing this bug, Translating content changes its font after importing the translated Word document, in the latest version of Storyline 360.

If you're still noticing this bug, please make sure you're using Storyline 360 (Build 3.61.27106.0) or later.

You can reach out Support Team in this discussion or privately in a support case.