Hi all, yesterday we encountered an odd problem. We built several courses in Storyline 360 in several languages, the font Open Sans was used for the main body. We tested all of them in Explorer, Firefox and Chrome. Everything was ok.
After that, the client asked us to merge them in one Storyline file, to make a Multilingual version. We merged the scenes, and created the multilingual version. We published the course again. Explorer was displaying everything correctly, but Chrome and Mozilla Firefox did not. The Open Sans font in the multilingual published course was not diplaying well, it was corrupted. The client is not happy and asking why now the course is not displaying well in those 2 browsers when it was displaying well in the stand alone versions. Please advise.
Wow, I am experiencing the same unique issue. We have a course that primarily uses our client's standard font, Slate Pro Medium. The course includes 14 branches, with each being a different language. It is published with Storyline 360 as HTML5 with Flash fall back. The Slate Pro font does not display properly in Firefox or Chrome. It does display properly in Edge and Internet Explorer. We published a single screen test using Slate Pro Medium, and the font displays properly in all browsers. It seems to be an issue when multiple languages are included in a single SCORM package. Have you made any progress on this issue?
If you open a ticket, you can then share it via email (such as an FTP login or wetransfer) to keep it private. They'll even sign an NDA if needed. We did this before 6 months ago over another problem we had.
I haven't heard of an issue specific to multiple languages in a course, but our Support Team is happy to take a look (and sign that NDA if needed). I'd also suggest taking a look at these troubleshooting steps for when the font is displaying incorrectly or characters are missing.
10 Replies
I'm curious to. Tagging so I see replies.
Hi Selene,
Thanks for reaching out and sharing your scenario.
I'm not sure that this is something we've seen previously. Would you be able to share your .story file with our team here so that we can take a look?
Hi Leslie, thank you for getting back to me! We are seeking permission to share the storyline files. I will let you know if they agree!
Sounds great Selene. The link I shared will get you working directly with a support engineer privately if needed and an NDA can be signed if required.
Wow, I am experiencing the same unique issue. We have a course that primarily uses our client's standard font, Slate Pro Medium. The course includes 14 branches, with each being a different language. It is published with Storyline 360 as HTML5 with Flash fall back. The Slate Pro font does not display properly in Firefox or Chrome. It does display properly in Edge and Internet Explorer. We published a single screen test using Slate Pro Medium, and the font displays properly in all browsers. It seems to be an issue when multiple languages are included in a single SCORM package. Have you made any progress on this issue?
No we haven't we haven't been able to get the end client to sign off on us sharing.
Our single language versions all display fine. After merging, we see the same problem you do.
My guess it's a CSS problem in the publishing compiler that's making it something IE/Edge likes, but not FF or Chrome.
I may be able to get our client to share as long as it is not made public. We need to launch soon . . . Our client is going to be very unhappy.
If you open a ticket, you can then share it via email (such as an FTP login or wetransfer) to keep it private. They'll even sign an NDA if needed. We did this before 6 months ago over another problem we had.
In fiddling with Firefox it seems to be showing the default Firefox font. You can change the font that is displaying by changing the default font.
Hi David and Matt,
I haven't heard of an issue specific to multiple languages in a course, but our Support Team is happy to take a look (and sign that NDA if needed). I'd also suggest taking a look at these troubleshooting steps for when the font is displaying incorrectly or characters are missing.
This discussion is closed. You can start a new discussion or contact Articulate Support.