{"id":4364,"date":"2016-10-18T22:08:00","date_gmt":"2016-10-18T22:08:00","guid":{"rendered":"https:\/\/alt2.minisoft.com\/support\/?p=4364"},"modified":"2020-10-21T16:35:03","modified_gmt":"2020-10-21T23:35:03","slug":"troubleshooting-pdf-fonts-arial-mt","status":"publish","type":"post","link":"https:\/\/c002.minisoft.com\/support\/troubleshooting-pdf-fonts-arial-mt\/","title":{"rendered":"Troubleshooting Fonts"},"content":{"rendered":"<p><strong>Added fonts do not show up when printed<\/strong><\/p>\n<p>If you added a licensed font to the Minisoft&#8217;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:<\/p>\n<pre>&lt;Font Name=\"Tahoma\" Spacing=\"Proportional\" \nPitchFactor=\"0.008332330903266\" ViewerFont=\"Tahoma\" PCLTypeface=\"1912\" \nPostscriptFont=\"Tahoma\" PostscriptBoldFont=\"Tahoma-Bold\" \nPDFFont=\"fonts\/tahoma.ttf\" PDFBoldFont=\"fonts\/tahomabd.ttf\" &gt;<\/pre>\n<p>Laser printers that do not include this typeface will not be able to print the font because it is unavailable to them. To make the typeface available, replace the PCLTypeface value with &#8220;-1&#8221;, which tells the printer to download the font from the computer sending the print job.<\/p>\n<p>After making this update in FontSpecs_User.xml, you must close eFORMz windows and restart the eFORMz service, if it is running.<\/p>\n<p><strong>PDF input file is unreadable<\/strong><\/p>\n<p>When using\u00a0a PDF as an eFORMz project input file\u00a0you might see some oddities when viewing the data. Below is an example of the potential issue.<\/p>\n<p><a href=\"https:\/\/alt2.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/eFORMz-Viewer.jpg\"><img decoding=\"async\" loading=\"lazy\" class=\"alignnone wp-image-4393 size-full\" src=\"https:\/\/alt2.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/eFORMz-Viewer.jpg\" alt=\"eformz-viewer\" width=\"597\" height=\"460\" srcset=\"https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/eFORMz-Viewer.jpg 597w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/eFORMz-Viewer-300x231.jpg 300w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/eFORMz-Viewer-150x116.jpg 150w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/eFORMz-Viewer-250x193.jpg 250w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/eFORMz-Viewer-550x424.jpg 550w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/eFORMz-Viewer-234x180.jpg 234w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/eFORMz-Viewer-389x300.jpg 389w\" sizes=\"(max-width: 597px) 100vw, 597px\" \/><\/a><\/p>\n<p>It&#8217;s possible that the eFORMz Composer\u00a0does 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:<\/p>\n<ol>\n<li>Open the PDF input file with Adobe.<\/li>\n<li>Right click on the document and select properties.<\/li>\n<li>Click on the font tab and you will\u00a0see a list of fonts being used in the document.<\/li>\n<\/ol>\n<p><a href=\"https:\/\/alt2.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/PDFDocProperties.jpg\"><img decoding=\"async\" loading=\"lazy\" class=\"wp-image-4387 size-wcstandard aligncenter\" src=\"https:\/\/alt2.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/PDFDocProperties-550x313.jpg\" alt=\"pdfdocproperties\" width=\"550\" height=\"313\" srcset=\"https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/PDFDocProperties-550x313.jpg 550w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/PDFDocProperties-300x171.jpg 300w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/PDFDocProperties-768x437.jpg 768w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/PDFDocProperties-150x85.jpg 150w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/PDFDocProperties-250x142.jpg 250w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/PDFDocProperties-800x455.jpg 800w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/PDFDocProperties-316x180.jpg 316w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/PDFDocProperties-527x300.jpg 527w, https:\/\/c002.minisoft.com\/support\/wp-content\/uploads\/2016\/10\/PDFDocProperties.jpg 814w\" sizes=\"(max-width: 550px) 100vw, 550px\" \/><\/a><\/p>\n<p>This\u00a0document uses the typeface\u00a0ArialMT. The issue here could be how the ArialMT font has been defined in the eFORMz Composer configuration files.<\/p>\n<ol>\n<li>Navigate to your Minisoft, eFORMz installation\u00a0directory,<\/li>\n<li>Open the FontSpecs.xml file.<\/li>\n<li>Scroll down about halfway through the file to the PDFInputFonts section as shown below.<\/li>\n<\/ol>\n<pre>&lt;PDFInputFonts&gt; \n     &lt;Font InputName=\"ArialMT\" <strong>CharacterSetName=\"UNICODE\"<\/strong> FontName=\"Arial\" Bold=\"false\" Italic=\"false\" \/&gt; \n     &lt;Font InputName=\"Arial\" CharacterSetName=\"WINDOWS 3.1 Latin 1\" FontName=\"Arial\" Bold=\"false\" Italic=\"false\" \/&gt; \n     &lt;Font InputName=\"Arial,Bold\" CharacterSetName=\"WINDOWS 3.1 Latin 1\" FontName=\"Arial\" Bold=\"true\" Italic=\"false\" \/&gt; \n     &lt;Font InputName=\"TimesNewRoman\" CharacterSetName=\"UNICODE\" FontName=\"Times New Roman\" Bold=\"false\" Italic=\"false\" \/&gt; \n     &lt;Font InputName=\"TimesNewRoman,Bold\" CharacterSetName=\"UNICODE\" FontName=\"Times New Roman\" Bold=\"true\" Italic=\"false\" \/&gt; \n     &lt;Font InputName=\"TimesNewRoman,BoldItalic\" CharacterSetName=\"UNICODE\" FontName=\"Times New Roman\" Bold=\"true\" Italic=\"true\" \/&gt; \n     &lt;Font InputName=\"TimesNewRoman,Italic\" CharacterSetName=\"UNICODE\" FontName=\"Times New Roman\" Bold=\"false\" Italic=\"true\" \/&gt; \n&lt;\/PDFInputFonts&gt;\n<\/pre>\n<p>Check the CharacterSetName for the ArialMT entry. If it is &#8220;UNICODE&#8221;, as shown, we will need to override this setting.<\/p>\n<p>In the same install directory:<\/p>\n<ol>\n<li>Open the &#8220;FontSpecs_User.xml&#8221; file.<\/li>\n<li>Locate the PDFInputFonts section of the file and add an additional ArialMT entry to override the configuration:<\/li>\n<\/ol>\n<p><strong>&lt;Font InputName=&#8221;ArialMT&#8221; CharacterSetName=&#8221;WINDOWS 3.1 Latin 1&#8243; FontName=&#8221;Arial&#8221; Bold=&#8221;false&#8221; Italic=&#8221;false&#8221; \/&gt;<\/strong><\/p>\n<p>If the ArialMT entry is already present, make sure that it matches the above entry. Specifically the CharacterSetName being &#8220;Windows 3.1 Latin 1&#8221;.<\/p>\n<p>The final section should read as such:<\/p>\n<pre>&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;Fonts&gt;\n&lt;PDFInputFonts&gt;\n    &lt;Font InputName=\"Helvetica\" CharacterSetName=\"WINDOWS 3.1 Latin 1\" FontName=\"Arial\" Bold=\"false\" Italic=\"false\" \/&gt;\n    &lt;Font InputName=\"Helvetica-Bold\" CharacterSetName=\"WINDOWS 3.1 Latin 1\" FontName=\"Arial\" Bold=\"true\" Italic=\"false\" \/&gt;\n    &lt;Font InputName=\"ArialMT\" CharacterSetName=\"WINDOWS 3.1 Latin 1\" FontName=\"Arial\" Bold=\"false\" Italic=\"false\" \/&gt;\n    &lt;Font InputName=\"Arial-BoldMT\" CharacterSetName=\"WINDOWS 3.1 Latin 1\" FontName=\"Arial\" Bold=\"true\" Italic=\"false\" \/&gt;\n&lt;\/PDFInputFonts&gt;\n&lt;Font Name=\"HelveticaNeueLTStd\" PDFBoldFont=\"fonts\/HelveticaNeueLTStd-Hv.otf\" PDFFont=\"fonts\/HelveticaNeueLTStd-Hv.otf\" ViewerFont=\"HelveticaNeueLTStd\" Spacing=\"Proportional\" PCLTypeface=\"-1\" PitchFactor=\"0.008332330903266\"&gt; &lt;\/Font&gt;\n&lt;Font Name=\"MinionPro-Regular\" PDFBoldFont=\"fonts\/MinionPro-Regular.otf\" PDFFont=\"fonts\/MinionPro-Regular.otf\" ViewerFont=\"MinionPro-Regular\" Spacing=\"Proportional\" PCLTypeface=\"-1\" PitchFactor=\"0.008332330903266\"&gt; &lt;\/Font&gt;\n&lt;\/Fonts&gt;\n<\/pre>\n<p>Save your current project and close the eFORMz Composer. Restart the Composer and reload your project. The data should appear normally.<\/p>\n<p>Tags: PDF Input<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Added fonts do not show up when printed If you added a licensed font to the Minisoft&#8217;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: &lt;Font Name=&#8221;Tahoma&#8221; Spacing=&#8221;Proportional&#8221; PitchFactor=&#8221;0.008332330903266&#8243; ViewerFont=&#8221;Tahoma&#8221; PCLTypeface=&#8221;1912&#8243; PostscriptFont=&#8221;Tahoma&#8221; PostscriptBoldFont=&#8221;Tahoma-Bold&#8221; PDFFont=&#8221;fonts\/tahoma.ttf&#8221; PDFBoldFont=&#8221;fonts\/tahomabd.ttf&#8221; &gt; Laser [&hellip;]<\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[143],"_links":{"self":[{"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/4364"}],"collection":[{"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/comments?post=4364"}],"version-history":[{"count":26,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/4364\/revisions"}],"predecessor-version":[{"id":8574,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/4364\/revisions\/8574"}],"wp:attachment":[{"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/media?parent=4364"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/categories?post=4364"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/tags?post=4364"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}