Resolve Postscript, PDF or PCL Input jobs with overprinted text and or font quality issues in Output Manager

print

 

Issue

Issue #1: Overlapping or overprinting text is an issue seen PostScript, PDF or PCL input job.

An example is the word abbonamento.

User-added image

 

Issue #2: Some fonts look thicker and,or appear jagged when displayed in the Output Manager Viewer; but are display smooth or nicely proportion with Adobe Acrobat Reader.


 

Cause

Cause #1: Job uses external Fonts

PostScript PDF and PCL Input jobs are expected to have its resources (especially fonts) embedded when using Output Manager.  
When the Output Manager Viewer displays text as overprinted and or the text characters are thicker or appear jagged; this is because the font resources are external and are not available for the job with Output Manager by default.  

There are commands in Output Manager that are designed to make use of these external resources that need to provided with the Postscript, PDF or PCL data file. As with other Postscript, PDF and PCL viewers Output Manager is designed to manage this issue.  

In the absence of the actual font and when presented with the font attributes specified in the Input job, Output Manager will substitute the fonts for the PostScript, PDF and PCL jobs with the Type1 fonts provided as part of the Output Manager Installation. 

Cause #2: Clipping path is smaller to contain text

  • If text seems to appear place outside the text box, or text displayed by the system like PI Output Manager Viewer but not by Acobat Reader, this is what it looks like when clip path for the text is small. 
  • When a PostScript of PDF job would have text overprints on top of each other; when more text is appearing, or disapearing in a way that some disappear outside of an invisible box, this is because those characters went out of the clipping path.  In PostScript and PDF jobs, fonts are set of instructions that draws characters on a defined are on the page.  This area is known as clipping path. If the clipping path is small to contain the texts, characters may overprint or cutoff off outside the box.  

Resolution

Resolution for Cause #1: Job uses external Fonts

It is strongly recommended that all fonts are embedded in the PDF data.
The 35 standard Type 1 fonts are supplied. No TrueType fonts are supplied. TrueType fonts should be embedded or provided along with the Postscript or PDF file. External Type 1 and TrueType fonts are supported. 95 standard CMaps are supplied.



There are different commands to define different types of external fonts.
  • TTFONTSMAP in the profile, for TrueType fonts - this command calls a file that has the font names and the font file drive:\path\fontfilename. Like:
  • PDFFNTP, PDFFNTE, PSFNTP, PSFNTE, PCLFNTP and PCLFNTE in the set file, for Type 1 fonts
TIP!The EXEC console or system.log will have messages on missing fonts and substition.
 For more information about the commands, refer to the appropiate "Input Client Command Guide".
 If after adding TTFONTSMAP successfully (which means no error message) and text disappears on PDF  or PostScript output, add PDFIN_CREATE_OUTLINE_VDFS=NO in the profile.
 

Resolution for Cause #2: Clipping path is smaller to contain text

MGR has PDFIN_CLIP_TEXT_PERCENT or PSIN_CLIP_TEXT_PERCENT commands to resolve this issue.  These are profile commands.  The default value of this command is zero (0), which means clipping is disabled.  A higher value would accommodate more characters in its text box, thus calculation of placement for each character will apply properly.

NOTE: Information of these commands will be in PostScript or PDF Input Command Guide.
 

UPDATED: April 24, 2017

Contact Us