Jeremias, Thanks for the fast response and for letting me know that the problem does not exist in the latest barcode4j source. I will start working on the build later today.
Thanks again.... Donnie -----Original Message----- From: Jeremias Maerki [mailto:[email protected]] Sent: Wednesday, April 28, 2010 1:37 AM To: [email protected] Subject: Re: Problems rendering PDF417 2D barcode in PDF file Hi Donnie, well, you've actually hit the wrong list. Your problem is about Barcode4J, not FOP. The right list would have been: [email protected] http://sourceforge.net/mail/?group_id=96670 Anyway... I've had to fix a number of bugs in the PDF417 implementation since the 2.0 release. And unfortunately, I haven't had time to cut a new release since then. You'll have to download the latest source code from the CVS repository and compile Barcode4J yourself for now. The current development code doesn't show any problems with the message you posted. http://barcode4j.sourceforge.net/trunk/building.html HTH On 28.04.2010 05:08:20 Bear wrote: > All, > > > > I am new to this mailing list so please forgive any over information. > > > > The environment I am working with is the following: > > > > Operating System: Red Hat AS4 Upd 4 > > Development Environment: Cache 2009.1.3, FOP 0.95 and barcode4j-2.0 > > > > I have been trying to render a PDF file containing a PDF417 2D barcode. > Attached is the "fo" and "xsl" files generated by Cache's Zen reports. When > the barcode is scanned, the first 41 characters scan fine, but then the data > becomes corrupted. The data being encoded is a variation of the ASTM > electronic order standard, so the data is a combination of letters, numbers, > vertical bars, carets and a carriage return at the end of each segment. > When the data is just characters, the barcode will scan correctly. Does > anyone have any idea as to what is causing the data corruption? Any help > will be greatly appreciated. > > > > Thanks in advance, > > Donnie Garrett > Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
