Poppins is a free TTF font that worked fine for us in Articulate Storyline 2. Now in 360 we are finding it works while building slides, but when you Preview it shows up as Times New Roman or some other seriffed font. Published content also shows up incorrectly, unless you run the Flash version.
Please advise as this font is client-chosen and would be a big problem for us to have to replace at this point.
Thanks for reaching out here and sharing a link to the font. That's really helpful! We've seen similar behavior in a few other fonts specifically within the HTML5 output (preview in 360 is also showing the HTML5 version). It is in the hands of our team for some additional investigation and I'll be sure to include the discussion here and font link so that we've got more examples and get some more eyes on this.
We'll be in touch here once there is a bit more information to share!
Hey Diana - I saw you mention this on another thread here, but I'm not able to locate your case. Would you be able to share your case number with us to take a look?
Hi Leslie - I tried to submit my case twice yesterday... the window finished processing, but I didn't received an auto-reply email with a case number... boo! Will try to resubmit now. case number 01019990
we have a similar issue here. We've published a new project (imported from storyline 2) and for me and my coworkers the font works fine (even if the font is not installed locally) but the customer sees Times New Roman in the HTML5 Version. Also there are no "f" in the Times new Roman font.I've attached some screenshots. I would be glad if you find a solution for this issue.
Great news - Articulate 360 Update 5 is now available! It includes a number of fixes detailed in the release notes here.
The item you may be interested in is how it fixed an issue where fonts such as Poppin and Kalam were not displaying properly. We're still working on some other fonts and we'll keep you posted!
Launch the Articulate 360 desktop app on your computer and click the “Update” button next to each tool.
Ha, that was the one thing I hadn't checked. Except that it was the opposite of what you'd said. Modern text was already on, turning it off fixed the problem.
Thanks, it's always the simple things that seem to trip me up!
Thanks, Jesse. I've seen the issue with modern player a few times, and typically you can toggle it off and then back on if you need to use it. Let us know if you're not able to use it at all and our team is looking into what this is causing such trouble for some!
Thanks Ashley, unfortunately in this case, toggling didn't resolve the issue. I'm working with support to figure out why this font is causing problems with the HTML5 font renderer when using Modern Text.
Simple or not with that workaround, it wasn't behaving as we expected.
Our team identified an issue folks were running into where that modern text would become invisible in the Storyline editor, but would still show when previewed or published. We've implemented a fix in the latest update of Storyline 360.
Take a look at the release notes here for some more detail and you can update by launching the Articulate 360 desktop app on your computer and click the Update button for Storyline. Details here.
15 Replies
Hi Keith,
Thanks for reaching out here and sharing a link to the font. That's really helpful! We've seen similar behavior in a few other fonts specifically within the HTML5 output (preview in 360 is also showing the HTML5 version). It is in the hands of our team for some additional investigation and I'll be sure to include the discussion here and font link so that we've got more examples and get some more eyes on this.
We'll be in touch here once there is a bit more information to share!
@Ashley - I'm having a similar issue and have submitted my files in a support case. Any news/updates?
Hey Diana - I saw you mention this on another thread here, but I'm not able to locate your case. Would you be able to share your case number with us to take a look?
Hi Leslie - I tried to submit my case twice yesterday... the window finished processing, but I didn't received an auto-reply email with a case number... boo! Will try to resubmit now. case number 01019990
Thanks so much :) Glad you were able to get that completed.
Looks like Cleo is currently testing :)
Hello,
we have a similar issue here. We've published a new project (imported from storyline 2) and for me and my coworkers the font works fine (even if the font is not installed locally) but the customer sees Times New Roman in the HTML5 Version. Also there are no "f" in the Times new Roman font.I've attached some screenshots. I would be glad if you find a solution for this issue.
Hello Anna-Marie,
Would you be able to share the font you are utilizing when you experience this issue? We are working to track and understand the issue.
Hey all,
Great news - Articulate 360 Update 5 is now available! It includes a number of fixes detailed in the release notes here.
The item you may be interested in is how it fixed an issue where fonts such as Poppin and Kalam were not displaying properly. We're still working on some other fonts and we'll keep you posted!
Launch the Articulate 360 desktop app on your computer and click the “Update” button next to each tool.
Let us know if you have any questions!
I am on the very latest version of SL 360 (the April 26 update) and I seem to be having a somewhat related issue, has anyone else seen this?
I'm using the font ChaletComprime HongKongSixty and while building it looks great, as soon as I preview the font, everything goes haywire.
Hi Jesse,
Thanks for the screenshot! Let's see if we can get this sorted out. Do you see an improvement if you enable Modern Text?
Ha, that was the one thing I hadn't checked. Except that it was the opposite of what you'd said. Modern text was already on, turning it off fixed the problem.
Thanks, it's always the simple things that seem to trip me up!
Thanks, Jesse. I've seen the issue with modern player a few times, and typically you can toggle it off and then back on if you need to use it. Let us know if you're not able to use it at all and our team is looking into what this is causing such trouble for some!
Thanks Ashley, unfortunately in this case, toggling didn't resolve the issue. I'm working with support to figure out why this font is causing problems with the HTML5 font renderer when using Modern Text.
Hi Jesse,
Simple or not with that workaround, it wasn't behaving as we expected.
Our team identified an issue folks were running into where that modern text would become invisible in the Storyline editor, but would still show when previewed or published. We've implemented a fix in the latest update of Storyline 360.
Take a look at the release notes here for some more detail and you can update by launching the Articulate 360 desktop app on your computer and click the Update button for Storyline. Details here.
Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.
This discussion is closed. You can start a new discussion or contact Articulate Support.