Forum Discussion
Replacing missing fonts can save the day
I searched but didn't find anything about fonts and performance. Sorry if this turns out to be a duplicate topic. So I was struggling with a simple 30 MB Storyline project (it wasn't my project and I was missing a couple of fonts). Everything was extremely slow, at times Storyline would hang for half a minute.
Turns out I replaced the missing fonts with plain Arial and the project "unlocked". Everything started running smoothly and publishing was much faster too.
This is just to let everyone know about this issue. Might I suggest developers to either improve this aspect of the App (previewing missing fonts) or block the user until the fonts are replaced. This way we might have a better UX for every user.
Best regards
Walter Bosello
5 Replies
Agree, missing fonts can cause the performance to degrade
Is there an easy way to see where the missing fonts were used? I also have a hand me down project and when it loads it announces 2 missing fonts. I'd like them replaced before hand off so that I know the end user has the same experience that I do. But I don't know how to find them.
You can export a translation document and then in word search for a font
I finally got a chance to try this today. I figured out that using Advanced find I can tell it to search for a font. I also figured out that it can only search for a font that you have installed. So, I installed the font I was trying to get rid of (Bebas) and it found nothing. I double checked my method using Arial and it had no problem finding that. When I uninstall Bebas and launch in Storyline, it's still showing that Bebas exists in my file. Is there a step that I'm missing?
I just found this article that solves this issue using the font replacement feature built into Storyline. Who knew it could be this easy? Storyline 360: Replacing Fonts | Articulate - Community
