Forum Discussion
Storyline 3 : Font Garbled on Publish
If you open the page in Chrome and use the Inspect menu item in the right click menu. Find the piece of the layout that holds the incorrectly mapped font and change the name of the font to Arial or something. If it suddenly shows up correctly, Storyline just doesn't create the font map correctly as it builds your html5. We have only seen this with one font, thus far (as mentioned).
Also, using inspect, you can see what the raw text looks like - if that's displaying correctly it's just the incorrect font map on build. The only solution is for Articulate to fix it - so all you can do for now is select a different font, or possibly don't "Bold" the font (if you are bolding it), or any other additional text treatment.
- eLearningMindsM7 years agoCommunity Member
Katherine, hope you can elaborate on the "font" map thing with html5. As i'm not technically well verse. Fonts that are created in the course are all "Arial" and "Calibri". Some are with bold.
If this is something Articulate should fix, any dates on the tentative solution?
- Crystal-Horn7 years agoStaff
Hi there, eLearningMinds Malaysia. Thanks for weighing in with your experience.
Our team is still investigating this issue. To confirm that the behavior of your fonts matches what we found with Katherine's file, would you be able to share your .story file with our team here? If it's the same issue, we'll include you in any notifications about an update.
Another customer pointed out a possible workaround that fixed this issue for his Storyline 360 output, so I'm going to share it here in case it helps you too:
It turns out that I had both the .otf and .ttf of the fonts installed on my machine. Whenever I publish a course with both fonts installed in Storyline 360, the font does not get rendered correctly in HTML5.
I removed 1 of the fonts and it seems to have resolved my issue. All the text in my published course in Storyline 360 looks okay now.Let me know if you submit a case, and I can follow along too.