One of our clients has a non-standard font they purchased for the modules we're developing for them in Storyline. My question is: Assuming I have that font installed on *my* PC, and I publish for HTML in Storyline... will the end users viewing that published output see exactly what I would see, or does every PC viewing that module have to have that non-standard font installed in order for it to be accurate? Is it a different answer if it is published to an LMS?
The fonts will be embedded within your Storyline course (essentially they get turned into images during publish) and the only exception to that may be some custom fonts on variable references (if they're a part of a larger text box it could impact that text as well).
You'll also want to make sure that Storyline is closed when you install the new font.
No worries Mario - and if you're at all worried about the custom fonts in a variable reference you could do a small test project and see how it behaves in some different environments.
3 Replies
Hi Mario,
The fonts will be embedded within your Storyline course (essentially they get turned into images during publish) and the only exception to that may be some custom fonts on variable references (if they're a part of a larger text box it could impact that text as well).
You'll also want to make sure that Storyline is closed when you install the new font.
Thank you, Ashley. That is what I was hoping but I didn't want to give out the wrong information. Much appreciated!
No worries Mario - and if you're at all worried about the custom fonts in a variable reference you could do a small test project and see how it behaves in some different environments.
This discussion is closed. You can start a new discussion or contact Articulate Support.