Please enable JavaScript to view this site.

 

Navigation: Tools > Font Tools

Font Name Issues

Scroll Prev Up Next More

Due to historical differences between competing font formats, as well as the Windows-Mac dichotomy, fonts have many internal names, almost always differing from one another, and differing inconsistently, as the example below shows, for the Univers LT Std 55 Roman font.

 

The various internal names of the Univers LT Std 55 Roman font as seen in FontLab 7

The various internal names of the Univers LT Std 55 Roman font as seen in FontLab 7

 

To work around these internal inconsistencies, QuarkXPress also uses inconsistent rules to extract the name it displays for each given font (the same is true, but to a lesser extent, for InDesign). As such, these differences are not problematic, but they do explain some of the small differences in the name of the same font, in Q++Studio, QuarkXPress and InDesign.

 

Below are descriptions of some of the font name issues that you may encounter, and what solution to use, or whether they can be ignored.

 

Font Has No PostScript Name

 

Some older screen fonts do not have a postscript font name that corresponds to their screen font name.

 

This is the case in the example on the right, where the Holidayboxes font is seen as Holidayboxes Plain by QuarkXPress and as Holidayboxes Regular by InDesign. Trying to use the font Holidayboxes in InDesign will cause message 185060 to be issued during diary generation.

 

This issue usually occurs for the symbol font of a holidays set and, as such, correcting this issue means changing the font in potentially hundreds of holidays sets properties.

 

The best solution is to modify the font so that the font name, as seen by QuarkXPress and InDesign, is the same as that of the screen font.

Alternatively, you can create the file text file OverrideFontFileNames.txt in the local folder C:\Q++StudioXV4\ in which you can list the font names and corresponding postscript names of the problem fonts, as shown at the bottom of the image on the right. This file must be copied on each individual workstation (listing fonts that are not installed will do no harm).

 

This is not an issue when using QuarkXPress, which accepts screen font names, but it is a problem when using InDesign, which requires a Postscript name.

 

Font Appears Twice

 

In some cases a font may appear twice, once as a screen font and once as a print-only font (ie. QuarkXPress 2018+ and/or InDesign).

 

In the example on the right, extracted from the installed fonts viewer:

 

One font, highlighted in green, is seen by Windows as Univers LT Std 55, while QuarkXPress and InDesign see it a the print-only font name and style Univers LT Std 55 Roman.

Another font is seen, highlighted in yellow, by Windows as Univers LT Std 49 Light UltraCn, while QuarkXPress and InDesign see it as the print-only font name and style Univers LT Std 49 Light Ultra Condensed.

 

In principle you should be able to use both variants interchangeably.

 

If you use an advanced font list combo-box to select a font, Q++Studio will automatically know which font name to supply to QuarkXPress and InDesign.

sDate = FormatText(sDate, 'f Univers LT Std 55, COLOR(Pantone 231U)', -1)
sWeekday = FormatText(sWeekday, 'f Univers LT Std 55 Roman=UniversLTStd', -1)

On the other hand, if you refer to a font in a macro function, such as FormatText, then you should refer to screen fonts by name only, and you should refer to print-only fonts by name and postscript name, separated by an equal sign, as shown above.

 

Scanned Font Name Differs From Font List

 

font names and font styles in the QuarkXPress 2018+

font names and font styles in the QuarkXPress 2018+

In some cases, the font name obtained from the script fonts usage or template font usage reports, and the font names listed in the font lists are different.

 

Here, again, if you use an advanced font list combo-box to select a font, Q++Studio will automatically know which font name to supply to QuarkXPress or InDesign, and there will be no issue.

 

And, in cases where you refer to a font in a macro function, such as FormatText, then you should refer to screen fonts by name only, and you should refer to print-only fonts by name and postscript name, separated by an equal sign, as shown above, always using the name obtained from the installed fonts viewer.

 

See also: advanced font list combo-box, installed fonts, font name issues, fonts usage report, fonts used in a template.

 


Topic 182995, last updated on 25-May-2021