Fonts not displaying correctly in Safari

[charliem82825372]

I'm using Century Gothic in a number of variables and they all display correctly in published projects as long as the font is installed on the computer where the published project is opened - both Mac and Windows machines.. This works fine in both the Chrome and Firefox browsers but NOT in Safari.

I've tried several things, including the methods well detailed here:

https://sepyle.medium.com/use-any-font-in-adobe-captivate-when-publishing-in-html5-8b03d2cabd7

Even when the Century Gothic font is installed on a Mac, it will display fine in Chrome but not in Safari. Instead, the default Helvetica font is used. There must be more to do to force the Century Gothic font to display correctly as dynamic text (from variables) in Safari. 

Any ideas would be most helpful.

Thank you!

Charlie

[Lilybiri]

Safari has a lot of quirks..

I just wonder why you are not using an Adobe font instead of a system font. That font family is available as Adobe font, and it would solve your problem. Have a look at this blog:

http://blog.lilybiri.com/fonts-in-captivate

[charliem82825372]

Hi Lilybiri, thank you for your response. I actually did already read your very helpful blog, where I learned about the distinction between static and dynamic fonts, which precisely describes the behavior I'm seeing. Indeed, the font I need to use is available as an Adobe Font -- if only I could actually activate it. 

I've just posted separately my dilemma where my CC account that I use for Captivate won't allow me to activate any fonts, even though it appears it should. A different CC account, that I sometimes use, that does NOT have Captivate with it, DOES appear to allow me to activate fonts. But that won't help me -- I have to get Adobe to fix my access to fonts in the CC account I use for Captivate.

Clearly, this is the best way to solve my font behavior issue since I need to make changes across forty projects, so I want to be sure it will really work.

Thanks for your help!

Charlie

[Lilybiri]

Understood, I have tried today to contact Adobe staff for a similar license problem experienced by another user. 

Sorry for having posted that superfluous link...