Latest News

the latest news from our team

Troubleshooting: PDF Fonts – Arial MT

When using a PDF as an eFORMz project input file you might see some oddities when viewing the data. Below is an example of the potential issue.

eformz-viewer

It’s possible that the eFORMz Composer does not have the correct fonts installed and mapped to properly display the data from the file. To determine what fonts are used in the PDF:

  1. Open the PDF input file with Adobe.
  2. Right click on the document and select properties.
  3. Click on the font tab and you will see a list of fonts being used in the document.

pdfdocproperties

This document uses the typeface ArialMT. The issue here could be how the ArialMT font has been defined in the eFORMz Composer configuration files.

  1. Navigate to your Minisoft, eFORMz installation directory,
  2. Open the FontSpecs.xml file.
  3. Scroll down about halfway through the file to the PDFInputFonts section as shown below.
<PDFInputFonts> 
     <Font InputName="ArialMT" CharacterSetName="UNICODE" FontName="Arial" Bold="false" Italic="false" /> 
     <Font InputName="Arial" CharacterSetName="WINDOWS 3.1 Latin 1" FontName="Arial" Bold="false" Italic="false" /> 
     <Font InputName="Arial,Bold" CharacterSetName="WINDOWS 3.1 Latin 1" FontName="Arial" Bold="true" Italic="false" /> 
     <Font InputName="TimesNewRoman" CharacterSetName="UNICODE" FontName="Times New Roman" Bold="false" Italic="false" /> 
     <Font InputName="TimesNewRoman,Bold" CharacterSetName="UNICODE" FontName="Times New Roman" Bold="true" Italic="false" /> 
     <Font InputName="TimesNewRoman,BoldItalic" CharacterSetName="UNICODE" FontName="Times New Roman" Bold="true" Italic="true" /> 
     <Font InputName="TimesNewRoman,Italic" CharacterSetName="UNICODE" FontName="Times New Roman" Bold="false" Italic="true" /> 
</PDFInputFonts>

Check the CharacterSetName for the ArialMT entry. If it is “UNICODE”, as shown, we will need to override this setting.

In the same install directory:

  1. Open the “FontSpecs_User.xml” file.
  2. Locate the PDFInputFonts section of the file and add an additional ArialMT entry to override the configuration:

<Font InputName=”ArialMT” CharacterSetName=”WINDOWS 3.1 Latin 1″ FontName=”Arial” Bold=”false” Italic=”false” />

If the ArialMT entry is already present, make sure that it matches the above entry. Specifically the CharacterSetName being “Windows 3.1 Latin 1”.

The final section should read as such:

<?xml version="1.0" encoding="UTF-8"?>
<Fonts>
<PDFInputFonts>
    <Font InputName="Helvetica" CharacterSetName="WINDOWS 3.1 Latin 1" FontName="Arial" Bold="false" Italic="false" />
    <Font InputName="Helvetica-Bold" CharacterSetName="WINDOWS 3.1 Latin 1" FontName="Arial" Bold="true" Italic="false" />
    <Font InputName="ArialMT" CharacterSetName="WINDOWS 3.1 Latin 1" FontName="Arial" Bold="false" Italic="false" />
    <Font InputName="Arial-BoldMT" CharacterSetName="WINDOWS 3.1 Latin 1" FontName="Arial" Bold="true" Italic="false" />
</PDFInputFonts>
<Font Name="HelveticaNeueLTStd" PDFBoldFont="fonts/HelveticaNeueLTStd-Hv.otf" PDFFont="fonts/HelveticaNeueLTStd-Hv.otf" ViewerFont="HelveticaNeueLTStd" Spacing="Proportional" PCLTypeface="-1" PitchFactor="0.008332330903266"> </Font>
<Font Name="MinionPro-Regular" PDFBoldFont="fonts/MinionPro-Regular.otf" PDFFont="fonts/MinionPro-Regular.otf" ViewerFont="MinionPro-Regular" Spacing="Proportional" PCLTypeface="-1" PitchFactor="0.008332330903266"> </Font>
</Fonts>

Save your current project and close the eFORMz Composer. Restart the Composer and reload your project. The data should appear normally.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

code