Forum Discussion
Are fonts embedded?
I'm going to chime in. We're also having problems with fonts not working properly. The original post is 6 years old so I'm surprised there are still problems with this, but I'm hopeful there's a fix I'm missing.
We're using Storyline 360 to create and publish courses in HTML5 (no Flash allowed) and upload them to a web-based LMS. We have a big client with custom fonts (their brand fonts, which are important because they use the training to train their customers), and the fonts aren't appearing for most of their trainees.... which is a big issue. The fonts work on our computers and on the company's computers, but not for most of the people they need to train.
We did a font test with a number of fonts, and none of them came out properly for the trainees in any area of the course. Every font was replaced by fonts with serifs, some characters were missing, and the spacing is all wrong. Some of the tested fonts were custom, but we also tested basic fonts like Open Sans and those didn't work either. So we currently have a really sleek course design that just looks tacky for all the end users... and we desperately need a fix.
Any idea on a fix for this? Are the fonts not embedded in the published project? Or is there an option to have the fonts embedded? At the very least, is there a list of super standard fonts that are safe to use for any device? We need a fix ASAP, and preferably one that involves using our customer's custom fonts without issues. Thanks in advance for your help.
Hi Julia,
I'm glad I'm not the only one! On my journey I did find a fix that you may find helpful.
1. Player Type
Check the player type that you've used. Since the latest upgrade we now have the option to use a 'Modern' player and a 'Classic' player. If you have selected 'Modern' your Storyline file will automatically publish in a HTML5 format. This is great for modern browsers but isn't compatible with some server restricted / older browsers, making the fonts appear in serif.2. 'Classic' player publishing options
If you have the 'Classic' player selected you can choose how your files are published. Your default publishing options will default to 'HTML5 with Flash fall back' I found that changing this to the other way around fixed our font problem.I hope this helps and happy to be corrected if any staff know otherwise!
Hi Hannah,
Thanks for sharing your tips!
We've been using the Classic player, so it looks like we're good to go there. I had no idea the Modern player has been having those issues, but that's great to know before we use it.
The problem must have something to do with the lack of Flash. Our customer is under strict restrictions for publishing in HTML5 only since Flash will be gone in 2020 and most browsers are already phasing it out. We're hopeful there will be a fix soon with our Articulate projects that keeps them looking nice without it. We've been seeing a number of features that are reliant on Flash to work properly, and it's making us a bit uneasy... so we're hoping that update comes soon!
