Skip to main content
S
s_mayer
Known Participant
January 19, 2016
Question

Problem with Font Versions in Distiller

  • January 19, 2016
  • 1 reply
  • 815 views

Hi,

Cross-posting this in another Acrobat forum, as I'm not sure where the question would be more appropriate.

I created a custom font for use with our technical documentation. During the font creation process, I created multiple versions of the font to test it. When I use FrameMaker to create a PDF, Distiller uses the wrong version of the font (that is, it uses an earlier version of the font, not the final version). When I look in the font settings for Distiller, it lists about 18 versions of the custom font, all of which seem to get embedded in the PDF, but Distiller seems to just grab one of the earlier versions.

FrameMaker doesn't have the same problem, as the new font looks fine there. It's just saving as PDF that stumbles.

What I've tried: uninstalling/re-installing the custom font; deleting all font cache files (.lst files); uninstalling/re-installing Acrobat.

Is there a way to flush the font list of all those old versions of the custom font?

Using Acrobat Pro/Distiller X, FrameMaker 2015.

Thanks for any advice.

     --Steve

This topic has been closed for replies.

1 reply

T
Test Screen Name
Legend
January 19, 2016

Distiller searches specific folders, which you can choose from the Distiller UI. Perhaps you can reorder. Distiller will also use, for preference, a font embedded on printing by the originating app.

S
s_mayerAuthor
Known Participant
January 19, 2016

Thanks for the suggestions. I think the problem is deeper than that, though. If I uninstall the custom font, delete all .lst font cache files, delete the Windows fntcache file, and then restart Distiller, all of the old versions of the custom font (that I just uninstalled) still show up in the font list. What I really want to know is, how can I flush this list completely and force Distiller to create it again?

When I delete all of the Adobe font cache files, I can see that Distiller is reading the available fonts from somewhere as it rebuilds the list of files on the system. That list includes the deleted font (and all of its versions), so it's not looking at a .lst file and it's not reading the fonts stored in the font locations. Where is it getting the list of fonts that display in the Settings dialog box?

T
Test Screen Name
Legend
January 19, 2016

So far as I know, it just scans the directories. How are you able to identify that the old version of the font is found - do the names change?

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices