Ahem.
I would personally really preffere if people did not just randomly go off and ask other projects to change or extend licencing so OOo could integrate that software. Such people *DEFINATELY* don't speak for OOo and passing themselves off as such is at best misleading. There is no general requirement that software that OOo makes use of be licenced under LGPL - for that matter, software contribution in teh OOo cvs are under both LGPL and SISSL, there is no "must be under LGPL" policy - there are plenty of such examples in OOo, starting off with berkley db, stlport and james clarck's xt. There are many others. There are presently no concerete plans to integrate or use fop in OOo that I am aware. Any such use will probably also be sufficently loosely coupled as to not (IMHO) cause LGPL related problems. On Thu, 4 Apr 2002, Charles Marcus wrote: > Here is one of the responses I received after inquiring about license > compatability from the Apache guys on the use of FOP... > > -----Original Message----- > From: alex [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 04, 2002 10:17 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: License Issue Inquiry > > >From: "Charles Marcus" <[EMAIL PROTECTED]> > > > I am taking it upon myself to submit a query regarding the Apache > > > Software License that FOP is licensed under. > > > > > > There is some big interest currently in the OOo (OpenOffice.org) > > > community with respect to finding a cross-platform, uniform and > > > integrated method for providing PDF document creation, and FOP looks > > > like it could be the answer. The only question is, can OOo use it? > > > > > > OOo requires that anything integrated into its source code be made > > > available to them under the terms of the LGPL license. > > > > > > What would be required in order to allow a version of FOP to be > > > licensed/sub-licensed/dual-licensed under the LGPL? > > We recently had this discussion in reverse about the possibility of > incorporating iText PDF library into FOP. This is a non XSL:FO library > which helps you generate and process PDF files. > > In the end I think we had to turn down iText's generous offer since its > code was licensed in an incompatible way with Apache FOP. > > However if your OpenOffice code uses LGPL and iText uses LGPL I see no > problems. > > http://www.lowagie.com/iText/ > > I guess the next question you need to ask yourself is do you require > XSL:FO > capability? > > > Alex McLintock > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Sander I see a dark sail on the horizon Set under a dark cloud that hides the sun Bring me my Broadsword and clear understanding --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
