10.07.2015 Views

Download - Multivac!

Download - Multivac!

Download - Multivac!

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

5.2 Font Format Details5.2.1 PostScript Type 1 FontsPostScript font file formats. PostScript Type 1 fonts are always split in two parts: theactual outline data and the metrics information. PDFlib supports the following file formatsfor PostScript Type 1 outline and metrics data on all platforms:> The platform-independent AFM (Adobe Font Metrics) and the Windows-specific PFM(Printer Font Metrics) format for metrics information. While AFM-based font metricscan be rearranged to any encoding supported by the font, common PFM metrics filesfor Western fonts (code page 1252) can only be used with the following encodings:auto, winansi, iso8859-1, unicode, ebcdic. PFM files for symbol fonts can be used withbuiltin encoding. PFM files for other code pages can be used with an encoding whichmatches the code page in the PFM (or any subset thereof), or with encoding builtin tochoose the PFM’s internal code page, or with unicode. For example, a PFM for a cyrillicfont can be used with the encodings cp1250, builtin, and unicode. Encoding auto willselect an appropriate encoding automatically.> The platform-independent PFA (Printer Font ASCII) and the Windows-specific PFB(Printer Font Binary) format for font outline information in the PostScript Type 1 format,(sometimes also called »ATM fonts«).> On the Mac, resource-based PostScript Type 1 fonts, i.e. LWFN (LaserWriter Font) outlinefonts, are also supported. These are accompanied by a font suitcase (FOND resource,or FFIL) which contains metrics data (plus screen fonts, which will be ignoredby PDFlib). PostScript host fonts can be used with the followings encodings: auto,macroman, macroman_apple, unicode, and builtin. However, macroman and macroman_apple may not be accepted for some fonts subject to the glyph complement of thefont.When working with PostScript host fonts the LWFN file must be placed in the samedirectory as the font suitcase, and must be named according to the 5+3+3 rule. Notethat PostScript host fonts are not supported in Carbon-less (Classic) builds of PDFlib.> OpenType fonts with PostScript outlines (*.otf).PostScript font names. If you are working with font files you can use arbitrary aliasnames (see section »Sources of Font Data«, page 101). If you want to know the font’s internalname there are several possibilities to determine it:> Open the font outline file (*.pfa or *.pfb), and look for the string after the entry/FontName. Omit the leading / character from this entry, and use the remainder asthe font name.> If you are working with Windows 2000/XP or Mac OS X 10.4 or above you can doubleclickthe font file and will see a font sample along with the PostScript name of thefont.> Open the AFM metrics file and look for the string after the entry FontName.Note The PostScript font name may differ substantially from the Windows font menu name, e.g.»AvantGarde-Demi« (PostScript name) vs. »AvantGarde, Bold« (Windows font menu name).Also, the font name as given in any Windows .inf file is not relevant for use with PDF.98 Chapter 5: Font Handling

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!