We're using a font that we've activated via Adobe Creative Cloud, Montserrat. When I brought on a few more developers, they activated theirs the same way but discovered it was displaying incorrectly. After a significant amount of wasted time it was discovered that Storyline had its own version of this font that it was installing. The conflict it created caused the font to display incorrectly, but there was no notification that there were multiple versions installed on the machine.
Is there a way to stop Storyline/Articulate 360 from installing fonts?
Yes Articulate does install a few fonts. Adobe CC will also install fonts onto your system, and if you are activating fonts to use, the fonts only remain on your system while they are activated. Since Storyline publishes to HTML5, those fonts have to be available somehwhere for the presentation to find them, or they will not display correctly when your content is played back. Those fonts will fall back to some other font. The fonts that Storyline installs are available to your content when published through a link that can referenct the font.
If you are going to use Adobe CC fonts, I suggest that you convert them into an image before you import that content into Storyline. Otherwise, I doubt that they well play properly.
I understand that there needs to be a fall back. The issue here is that SL appears to not recognize that a font already exists in the fonts folder. Either that or it's looking in the wrong location.
Also, apart from the fact that this is text created inside of Storyline, not imported content, all of my courses have to be converted to multiple languages, so converting to an image is not an option here.
What I would like is the ability to tell SL not to install its own versions.
2 Replies
Hi Nathan,
Yes Articulate does install a few fonts. Adobe CC will also install fonts onto your system, and if you are activating fonts to use, the fonts only remain on your system while they are activated. Since Storyline publishes to HTML5, those fonts have to be available somehwhere for the presentation to find them, or they will not display correctly when your content is played back. Those fonts will fall back to some other font. The fonts that Storyline installs are available to your content when published through a link that can referenct the font.
If you are going to use Adobe CC fonts, I suggest that you convert them into an image before you import that content into Storyline. Otherwise, I doubt that they well play properly.
Dave
I understand that there needs to be a fall back. The issue here is that SL appears to not recognize that a font already exists in the fonts folder. Either that or it's looking in the wrong location.
Also, apart from the fact that this is text created inside of Storyline, not imported content, all of my courses have to be converted to multiple languages, so converting to an image is not an option here.
What I would like is the ability to tell SL not to install its own versions.
This discussion is closed. You can start a new discussion or contact Articulate Support.