TECH TIP: Overcome font problems with font mappings

Font nomenclature is not standardized on the Windows platform. This results in the same font being referenced by two different names in two different applications. It is likely that your PDF file may specify a font which is available on your system with another name.

For example, Arial Bold may be defined in three different PDF files as EJFTYX+Arial-Bold, Arial,Bold and Gen_Arial+Bold. pdf2picture uses the font name defined in the PDF file when generating the WMF file.  However, MS Office does not recognize “EJFTYX+Arial-Bold” as being Arial Bold, and consequently renders it as Courier or Times Roman. To overcome this problem, pdf2picture will alert you if it finds font names in the PDF file that it does not recognize. You will get a warning after the conversion is complete, pointing you to a text file in the /logs/ folder of your pdf2picture installation (usually C:/Program Files/Visual Integrity/pdf2picture) where you can find and print a list of all incompatible font names. You can then start pdf2picture again, select the same PDF file, and go to the Font Mappings tab in the Options menu to add font mappings which will be applied during conversion. Below is an example of the Font Mapping screen: