Legal
The views expressed in this blog are my own and do not necessarily reflect the views of Adobe Systems Incorporated.
Search
May
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
Archives
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- November 2006
- October 2006
- August 2006
- July 2006
- May 2006
- April 2006
- March 2006
- January 2006
- December 2005
- November 2005
- October 2005
May 08, 2008
InDesign Font Conflicts
Periodically somebody asks how InDesign prioritizes fonts whose names conflict, or what consistutes a conflict, and nobody knows. Recently David Blatner (InDesignSecrets.com, co-author of Real World InDesign, Real World QuarkXPress, etc.) asked the same question, and sparked me to pull together the answers.
There are three kinds of name conflicts in InDesign that cause fonts to potentially not show up in the font menu.
1) Duplicate PostScript FontName
2) Duplicate menu name (as shown in InDesign)
3) Multiple "regular"-like styles in a single family
The third case is a bit different, so we'll take it separately.