Forum Discussion
Storyline 3 : Font Garbled on Publish
This is probably one for the bug list - but I couldn't find a better place to log that, so I'm starting here - please push me into the right spot for this kind of issue!
We opened a SL2 file in our new SL3 and published our course file with NO FLASH (yay!). We viewed the course in Chrome and Edge, to find that the character map for the font "Gotham" in Bold was completely freaked out. All text was nutty. You could debug in the browser and assign any other font and the text would be fine, but switch back to Gotham Bold and the character map is all offset (like "Correct" is reliably "N]uuyni").
We worry that there will be other lurking fonts like this (so far we've found no others), so we wanted to log it with Articulate in case your architects can figure out why this happened and help with a fix. Happy to send the file for bug fixing purposes - should I do that here?
34 Replies
I noticed a Danielle Thomas mentioned issues with Gotham Black (we did not have issues with Gotham Black, just Gotham bold) in a different thread which doesn't seem to be about the same thing...
https://community.articulate.com/discussions/articulate-storyline/font-issue-in-storyline-360
Sorry that's happening, Katherine! I took a peek into Danielle's case, and I saw that uninstalling/reinstalling the fonts solved the issue for her. Also, Sid shared a similar solution further down in that thread.
Could you try uninstalling/reinstalling, and let me know if that does the trick?
I have tried the uninstall-reinstall and the font still is mapped incorrectly on publish, This is repeatable on two separate systems. When you are working with the file in Storyline, Gotham in bold displays fine. When you publish it, the font mapping is off.
Here is a simplified repeatable example of the use of the font Gotham, with the B button clicked. Meaning we "bold"-ed the font within Storyline, not using a separate BOLD version of the Gotham font - like Gotham Black would be.
Thanks, Katherine. You mentioned that Gotham in bold displays fine in Storyline preview, but it looks incorrect after the file is published.
How did you publish the file, and where did you host the output? Could you send me a link to the published file?
If you published for Web, the easiest way to get a link is to host the output on Tempshare. You could also publish to Articulate 360 and quickly grab a link that way.
I output the file 100% html 5 to my desktop and run the story-html5.html file in various browsers. Here is a zip of an example.
Thanks, Katherine. I'm seeing the same thing you're seeing, so I'd like to have our Support Engineers weigh in. I'm going to start a case on your behalf, so be on the lookout for an email from our team soon!
Looking forward to the Engineers weighing in!
Have there been any updates on this issue? My team has experienced something similar with Gotham font in our exported Storyline 3 files, but the garbled font appears sporadically.
Thanks in advance!
Total and complete radio silence from Articulate.
Non-repeatable issues are more typically about font installation. Gotham otherwise maps correctly - when not bolded.
This is very specifically when using "Gotham" (not Gotham Black, Light, Medium, Extra Bold...etc. - just "Gotham") and selecting the little B for bolding it within Storyline. Storyline just doesn't map Gotham - when it's bolded in this way - correctly on publish. Our high tech solution is to not bold the Gotham font.
Thanks, Katherine!
