windows 10 and quarkxpress 8 font issues

If this is the case, it will not matter which font is chosen. This situation would most likely occur when the same font is resides in two separate locations. If none of these rules can be applied, then the first font enumerated by CoolType is chosen. TrueType (including OpenType with TrueType outlines) Type 1 (“PostScript”) / OpenType CFF (Compact Font Format) If same number of glyphs, choose the font with preferred technology using this order Note that this does not address the problem for other applications.ĥ. This means that in InDesign, Type 1 fonts will outrank Apple’s system dfonts when they have conflicting names (as they often do). Choose font that is not a dfont (Macintosh only rule) This means that fonts under user control get to override fonts hidden away in Adobe’s “required” fonts folder.ģ. Choose font not in Adobe:Fonts:Reqrd: folder (Macintosh only rule) Prioritize font installed in an OS font folder over font installed in a private Adobe font folder. If a given rule does not decide between the two fonts, go to the next rule, until one of the fonts is chosen, your brain explodes, or you run out of rules, whichever comes first.Ġ. The rules are priority from highest to lowest. If two fonts have the same Family and Style name and the same PostScript FontName, the following rules are followed to determine which font is used. (Yes, Microsoft has been notified of the bug, and doubtless they will fix it.) In such a case, whichever one is listed first by the core Adobe font engine will show up in the menu – in this case it’s the regular, and the bold is missing. For example, Microsoft YaHei Bold that shipped with Vista has a bug in that it has the same PostScript FontName (under some language IDs in the name table) as the regular weight of the same font.

When the two fonts conflict in their PostScript FontName, InDesign will never show both, regardless of format. If two fonts have the same Family and Style name, but different PostScript FontNames, both fonts are shown in the menu (an abbreviation is added to the menu to indicate font type). (This first section owes a great debt to Michelle Hill, who documented the issues in an internal Adobe document several years ago.)

The third case is a bit different, so we’ll take it separately. There are three kinds of name conflicts in InDesign that cause fonts to potentially not show up in the font menu.Ģ) Duplicate menu name (as shown in InDesign)ģ) Multiple “regular”-like styles in a single family Recently David Blatner (, co-author of Real World InDesign, Real World QuarkXPress, etc.) asked the same question, and sparked me to pull together the answers. Periodically somebody asks how InDesign prioritizes fonts whose names conflict, or what consistutes a conflict, and nobody knows.

Windows 10 and quarkxpress 8 font issues