On Tue, May 20, 2008 at 8:04 AM, Thorsten Behrens <[EMAIL PROTECTED]> wrote: > On Mon, May 19, 2008 at 09:43:44PM +0100, Terry Burton wrote: >> Lacking support for EPS seems quite a surprising limitation - bother :-/ >> >> Do you know whether support for this on the horizon? >> > there've been plans to have some ghostscript integration for a > longer time - but I don't believe this has had higher priority > (though your offer might actually change this). The issue with > ghostscript is the license - OOo can only make use of it > out-of-process, with gs being GPL.
Hi Thorsten, all, Great! It's good to know that barcoding might be the driver for wider-reaching improvements to the project - I'll very much look forward to seeing whether this proposal gathers momentum. >> BWIPP is neatly split into a large set of encoder procedures (one for >> each barcode symbology) and a few renderer procedures. The <...snip...> > Ah, interesting! This would make batch-processing the barcode > out-of-process pretty straight-forward. Just to make the IPC-based approach more explicit, I have attached a simple PS example that enumerates the main data contained in a one-dimensional barcode structure. The GS output of this will hopefully give people some feel for how simple the internal image/object generation ought to be. > IANAL, but shipping a gs > executable alongside OOo (for e.g. Windows) should be ok. I believe this to be the approach taken by at least a couple of commercial barcoding tools for Windows that ship an independently functioning GPL GhostScript bundle on their installation media as explicitly permitted in the detail given here [1]. So at least from the licensing prospective there ought to be no problem for OOo. Thanks for your consideration and do let me know if you should need any further information. Warm regards, Tez [1] http://pages.cs.wisc.edu/~ghost/doc/cvs/Commprod.htm#examples
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
