Please enable JavaScript to view this site.


Navigation: Messages > DTP Messages > Generating Messages

Cannot find postscript font name (InDesign)

Scroll Prev Up Next More
This singleton run-time message occurs when generating a diary using InDesign, if an instruction is encountered to set the font of a given token replacement to a font does not exist on your PC.


This message is generated during diary generation, just before InDesign is launched, but you should have had a corresponding design-time message originating from any of the properties where you can specify a change of font (such as minicalendars and macros).


Note that this warning is not the same as the one (shown in the example on the right) that you get when opening an existing InDesign file that contains references to fonts that are not installed on your PC.


The InDesign message on the right will go away as soon as the file is opened on a PC with this font installed.


But the present message that concerns us here, in this topic, means that the reference to the missing font could not be inserted in the InDesign file.


Therefore, even if the generated output file is later opened on a PC that does have that font, the font will still not appear in the document.


Fonts whose name begins with @


Fonts whose names begin with the at character (@) are the legacy vertically oriented fonts of early versions of Windows 32-bits.


These screen-only fonts should not be used for print with QuarkXPress or InDesign.


In most cases these fonts are filtered-out by Q++Studio and the only place where these may appear is in the holidays set properties dialog when the Use font in output file is used, as shown in the example on the right.


You should always use the version of the font whose name does not begin with the @ character.



The issue usually arises due to the use of some older screen fonts do not have a postscript font name. The solution is to create the file text file OverrideFontFileNames.txt in the folder C:\Q++StudioXV4\ in which you can list the font names and corresponding postscript names of the problem fonts, as discussed in the topic on font name issues.


Topic 185060, last updated on 17-Apr-2023