#17 Difference between barcode in PDF and PCL

closed
nobody
5
2014-08-12
2010-03-24
Anonymous
No

Hi all.

I use

<fo:block>
<fo:instream-foreign-object>
<barcode:barcode>
<xsl:attribute name="message">
<xsl:value-of select="barcode" />
</xsl:attribute>
<barcode:intl2of5>
<barcode:height>10mm</barcode:height>
<barcode:module-width>0.38mm</barcode:module-width>
<barcode:wide-factor>3.0</barcode:wide-factor>
<barcode:human-readable>
<barcode:placement>none</barcode:placement>
</barcode:human-readable>
</barcode:intl2of5>
</barcode:barcode>
</fo:instream-foreign-object>
</fo:block>

to print the intl2of5 barcode 024305251003030206.

When I produce the PDF document the barcode is correct, otherwise when I produce the PCL the barcode can't be read by the scanner.

Thanks in advance.
HL

Discussion

  • Jeremias Märki

    Jeremias Märki - 2010-03-25

    This is most probably a resolution issue. In PDF, the barcode is generated as vector graphics which ensures that the maximum resolution is automatically achieved. With PCL, however, the barcode has to be converted to a bitmap which makes the whole thing resolution-dependent and therefore prone to scanning problems. Please look at http://barcode4j.sourceforge.net/troubleshooting.html#printing-quality for hints on how to tweak the Barcode XML values to make the barcode work in PCL. You will need to know the resolution at which you generate your PCL file to find the right values. Please get back here if this doesn't help. Good luck.

     
  • Jeremias Märki

    Jeremias Märki - 2010-03-25
    • status: open --> pending
     
  • SourceForge Robot

    • status: pending --> closed
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks