Pub2ID Fonts & Styles

Dealing with Fonts and Styles

1. Microsoft Publisher is a Windows only application. The ideal conversion is one that takes place on the same machine that was used to author the original MS Publisher document or one that has all of the same fonts installed.

2. MS Publisher does not have a font collection feature, rather it relies on a feature of the “Commercial Printing Tools” menu to imbed fonts in a way similar to other Microsoft applications such as MS Word. Embedding fonts in this way has no beneficial impact on the conversion process. Adobe InDesign requires the fonts to be installed and active on the Pub2ID host system.

3. Conversion of these files to Adobe InDesign on a Macintosh presents a particular challenge to the user since…

a) Windows fonts do not generally install on a Macintosh.

b) The proliferation of free Windows fonts of dubious quality which may not behave as expected nor have any Macintosh counterpart.

4. You should expect that the author of the MS Publisher document used “menu stylizing of text,” exclusively. This makes mapping of the font and style(s) somewhat imprecise. Adobe InDesign does not support menu styles; therefore the use in MS Publisher of the typeface “Helvetica” with a menu style of “Bold” will result in InDesign attempting to map to a font named “Helvetica Bold”. Unless a font installed on your system has that exact name, the font will have to be remapped manually.

5. Other supported font effects such as underlines will only appear when the font is active and recognized in the InDesign document.

**By default missing fonts in InDesign show as highlighted in pink.

Suggested Font Substitution Strategy

The best strategy for remapping fonts is to convert the MSP file, save the converted document as a new INDD document then close that document. Reopen this new InDesign document and use the InDesign automatic font substitution dialog to remap fonts used to similar ones you may have active on your system.