I just wanted a clarification about one of the HTML5 restrictions - can't change player font published for HTML5.
Let's say I change the player font from the default font to Arial.
When I publish the course with the option HTML5, users viewing the course with a browser that does not have FLASH, will see the HTML5 output and, therefore, will see the default font - not the Arial font. Is that correct?
Great question Yes, you are completely correct. If a user views an HTML5 course and there have been changes to the player fonts, they won't see those player fonts. They'll see a system default font.
The system default font - is this always Verdana in html5? If I chose an iOS font as Arial - I would like the system to use this font as it is much thinner on an iPad than Verdana? Is this possible?
The default font you'll see in the player set up on slide content is the Articulate font, and you'll see the different font elements such as player text labels or variable references and how those fonts will behave on the ipad in HTML5 or the mobile player as indicated here. If you use a font that is not supported it will be displayed using the default fonts of the system or device on which the content is being viewed.
Arial is a cross platform font and (thus) supported on iOS-devices - never the less it is not displayed on the iPad in HTML5 output. Does anyone know which font is being displayed? - it sure looks like verdana.
I'm not sure I understand I set the player font to Arial in Storyline, and Arial is a supported font on my device (http://support.apple.com/kb/HT5878), but it still looks like Verdana in my html5 output, when I test it on iOS7 iPad?
Any fonts included in your published file on slides, should be displaying on the HTML5 content as we essentially convert text to images upon publish, to avoid the need for local fonts. For the player font, as indicated in the comparison chart you can't set the font for HTML5 or the mobile player:
Hi, curious if this is still how html5 works with fonts? Are they still converted to images upon publish? Is this true in the modern player? I'm wondering about onscreen fonts more than player fonts.
With Storyline 360 we've made a lot of improvements and advancements with our HTML5 output and specifically on the fonts. We're now using some new methods to ensure that fonts display as expected on all devices and browsers, you can read a bit more about that here.
If fonts aren't displaying, it may be something as simple as the server not allowing for access to Web Open Font Format (WOFF) files, so they can add that MIME type to the server. There are a few other solutions here for if the fonts are misbehaving.
Let me know if you've run into any other trouble - we're here to help!
Any advice? My fonts are not working properly so I have to replace all fonts in my course without having to redo everything. Any fonts that play nice in HTML5 in IE and Chrome?
What issues are you running into with your fonts? I saw you also posted here about kerning, so if you're using Storyline 3 or 360 the modern text should fix it.
13 Replies
Hi Ejuana. I hope you're doing well!
Great question
Yes, you are completely correct. If a user views an HTML5 course and there have been changes to the player fonts, they won't see those player fonts. They'll see a system default font.
Thanks!
Hi Christine
The system default font - is this always Verdana in html5? If I chose an iOS font as Arial - I would like the system to use this font as it is much thinner on an iPad than Verdana? Is this possible?
Thanks in advance.
Hi Dorte,
The default font you'll see in the player set up on slide content is the Articulate font, and you'll see the different font elements such as player text labels or variable references and how those fonts will behave on the ipad in HTML5 or the mobile player as indicated here. If you use a font that is not supported it will be displayed using the default fonts of the system or device on which the content is being viewed.
Arial is a cross platform font and (thus) supported on iOS-devices - never the less it is not displayed on the iPad in HTML5 output. Does anyone know which font is being displayed? - it sure looks like verdana.
Hi Asley
I'm not sure I understand
I set the player font to Arial in Storyline, and Arial is a supported font on my device (http://support.apple.com/kb/HT5878), but it still looks like Verdana in my html5 output, when I test it on iOS7 iPad?
Hi Mette and Dorte,
Any fonts included in your published file on slides, should be displaying on the HTML5 content as we essentially convert text to images upon publish, to avoid the need for local fonts. For the player font, as indicated in the comparison chart you can't set the font for HTML5 or the mobile player:
Hi, curious if this is still how html5 works with fonts? Are they still converted to images upon publish? Is this true in the modern player? I'm wondering about onscreen fonts more than player fonts.
Hi Laurel,
With Storyline 360 we've made a lot of improvements and advancements with our HTML5 output and specifically on the fonts. We're now using some new methods to ensure that fonts display as expected on all devices and browsers, you can read a bit more about that here.
If fonts aren't displaying, it may be something as simple as the server not allowing for access to Web Open Font Format (WOFF) files, so they can add that MIME type to the server. There are a few other solutions here for if the fonts are misbehaving.
Let me know if you've run into any other trouble - we're here to help!
Thanks Ashley! This information is really helpful.
Happy to help, Laurel!
Any advice? My fonts are not working properly so I have to replace all fonts in my course without having to redo everything. Any fonts that play nice in HTML5 in IE and Chrome?
Hi Stephanie,
What issues are you running into with your fonts? I saw you also posted here about kerning, so if you're using Storyline 3 or 360 the modern text should fix it.
If the font isn't displaying correctly in certain browsers take a look at the troubleshooting steps here.
This discussion is closed. You can start a new discussion or contact Articulate Support.