They're entirely correct: don't do this, use subset embedding because different setups can have different versions of Arial all of which will resolve against the ArialMT identifier, but with completely different internal glyphIDs.Īs PDFs point to glyphids, not 'letters', what looks like cake with your copy of Arial could -when encoded as glyphid array- end up being B^r( in a different version of Arial. There are computers that don't have much fonts and the result may be weird The data should appear normally.Just because you can do something doesn't mean you should. Restart the Composer and reload your project. Save your current project and close the eFORMz Composer.

Specifically the CharacterSetName being “Windows 3.1 Latin 1”.

If the ArialMT entry is already present, make sure that it matches the above entry. Locate the PDFInputFonts section of the file and add an additional ArialMT entry to override the configuration:.If it is “UNICODE”, as shown, we will need to override this setting. Scroll down about halfway through the file to the PDFInputFonts section as shown below.Ĭheck the CharacterSetName for the ArialMT entry.Navigate to your Minisoft, eFORMz installation directory,.The issue here could be how the ArialMT font has been defined in the eFORMz Composer configuration files. Click on the font tab and you will see a list of fonts being used in the document.

Right click on the document and select properties.

To determine what fonts are used in the PDF: It’s possible that the eFORMz Composer does not have the correct fonts installed and mapped to properly display the data from the file. Below is an example of the potential issue. When using a PDF as an eFORMz project input file you might see some oddities when viewing the data. To make the typeface available, replace the PCLTypeface value with “-1”, which tells the printer to download the font from the computer sending the print job.Īfter making this update in FontSpecs_User.xml, you must close eFORMz windows and restart the eFORMz service, if it is running. Laser printers that do not include this typeface will not be able to print the font because it is unavailable to them. If you added a licensed font to the Minisoft’s fonts directory, you must also update the FontSpecs_User.xml file with the font details, like this for the Tahoma, which has a PCL typeface ID of 1912:

Arialmt