Not able to use custom fonts with variable references
Mar 29, 2016
Hi,
I am currently designing a suite of eLearning modules for a client and have run into the issue of not being able to use custom fonts with variable references.
After researching on this forum, it seems that this is a well documented issue which has been known about for three years. Considering how much of a fundamental design error this is, I'm interested to know why this issues has not been addressed, or if there are any plans to do so in the near future? Whenever anyone has asked this question on another thread, it tends not to be addressed. If there are no plans to fix this issue, I would be keen to understand the reason behind this decision.
We are now faced with a choice of font consistency or increased personalisation through the use of a Name variable. I did see on one of the discussions that someone had claimed to find a fix - which involved embedding the custom font in the story line output using CCS, before publishing it. Has anyone had any success with this?
I would also like to know whether 'Arial' would work on most computers. Storyline is currently reverting my custom font to Times New Roman. If I set my text to Arial within storyline and then publish it, would it still show Arial on everyones computers considering it is a web safe font, or would it still revert it to times new roman?
Kind Regards,
Oli
1 Reply
This post was removed by the author
Hi Oli,
You may find that text changes size when it includes a variable reference, depending on the length of the variable's current value. This is by design to ensure that the text is always visible to learners, no matter how lengthy it is.
For example, let's say you're using a variable to display text, then you update the variable with new text at a specific point on the timeline or during an interaction. Depending on the length of the text, it may shrink to fit within its container.
To avoid shrinking variable text, make the text box big enough to accommodate the longest variable value.
You may find that fonts applied to variable references in your published Articulate Storyline 2 output aren't the fonts you expected.
Fonts can't be embedded in published output for variable text. As a result, default system fonts will be substituted for variable text. Default system fonts may be different for each computer, tablet, or smartphone where your content is viewed.
This discussion is closed. You can start a new discussion or contact Articulate Support.