September 24, 2019
Font Issue Captivate 2019 Update
Comments
(6)
September 24, 2019
Font Issue Captivate 2019 Update
Newbie 2 posts
Followers: 2 people
(6)

Hi,

Late to the game with updating to Captivate 2019 11.5.0. I’m working with my company’s IT department to get the newest patch, but I don’t know that the patch will fix my issue based on information I could find in other threads in the forum.

With this new font thing in the newest version, our company font (that was installed on my laptop locally) is reverting to Tahoma when I open old projects. Except, my intro slide doesn’t convert to Tahoma and stays our company font (really strange and I can’t find what would be different on that slide versus the other slides that convert to Tahoma). Our company font is visible in Captivate and I can change all of my shapes and captions back to our company font, but our team shouldn’t have to go through all this effort for every single course created in the last two years.

Can anyone confirm if there is a work-around yet, a fix, or tell me whether this is fixed in a patch I have yet to install?

Thank you,

Michelle

6 Comments
2020-10-19 17:21:12
2020-10-19 17:21:12

I am have this same issue. It is very annoying when you do not know what Captivate is actually doing.   Is there any workaround possibly for this one?

Like
(1)
(1)
>
garym26018370
's comment
2020-10-20 08:54:12
2020-10-20 08:54:12
>
garym26018370
's comment

Did you read the blogs for which I posted a link in my first answer (which was never read as was the case with other answers)?

Like
2020-04-28 13:23:01
2020-04-28 13:23:01

Hi Michelle,

Please let us know if you are still experiencing the issue. we will reach out to you and help.

Regards,

Shaleen

Like
2020-04-28 13:21:07
2020-04-28 13:21:07

Hi Michelle,

 

Please let us know if you are still experiencing the issue. we will reach out to you and help.

 

Regards,

Shaleen

Like
2019-09-26 08:34:09
2019-09-26 08:34:09

Themes have changed a lot in 11.5.0 and 11.5.1.  I suspect you are using a system font. That means that only learners who have that font installed on their system as well, will see the correct font. At least if you are talking about dynamic text and/or responsive projects where fonts need to be generated at runtime, and cannot be converted to images (as was always the case for static text and SWF output). Personally I never had the issue with fonts being converted to Tahoma, but I only use websafe and Adobe fonts (formerly indicated as Typekit fonts). You could try to change the font back to your system font, because in Theme Properties that is now perfectly possible, and the font will be replaced in all object styles using that font. Will post some links to blogs I wrote about the new theme features and about fonts. In a separate comment, because it may take some time to appear due to moderation.

Like
(1)
Add Comment