Re: Apache FO Barcode FO samples in FO?
Jeremias Maerki <[email protected]> Mon, 08 Sep 2003 17:09:13 +0200
| Newsgroups | gmane.comp.krysalis.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Richard, sorry for the late response. I've been away on holidays and still the only developer on Krysalis Barcode, I'm afraid. On 04.09.2003 00:18:44 KATZ, RICHARD D - SAN MATEO, CA wrote: > Do you have the input (.FO?) that generates the bar code test PDF - so > that someone could run it and try to get the same output? That would > help a lot. From your other post I see that you managed to generate the XSL-FO file for the test PDF. Do you think it's a good idea if I included an XSL-FO file that contains the barcodes as SVG graphics? I mean, Krysalis Barcodes "magic" (at least with the Xalan extension) is already done at that point. It might even create confusion with the new XSL-FO examples I have in CVS that demonstrate the new FOP extension. By the way, have you checked out the latest code? You can download CVS snapshots from http://www.krysalis.org/tarballs/krysalis-barcode/ Documentation on the new features is not written, yet, but will appear on the website real soon now. I want to get out v1.0 this month if possible. > I'm just trying this for the first time. It seems things that look like > they should work don't necessarily produce the desired result. I've been > trying various mechanisms that don't quite get the proper result. > > For instance: > > 1. I've been trying to follow the instructions on > http://krysalis.org/barcode/xsl-fo.html - but they're a bit complicated. > I'd like something that I know "works" to validate against. Hmm. I shall try to come up with better documentation and more ready-to-use examples. In an ideal world, what would you expect? > I try printing your result PDF, it comes out OK. > > But what does it look like as input FO? I think you have managed to find that out, right? I'd be grateful if you'd share your experiences with and thoughts about Krysalis Barcode with me so I can improve the package. Of course, a few helpful fingers (producing documentation improvements, examples or even code) can never hurt. :-) Jeremias Maerki ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf