cvs commit: xml-fop/docs/examples/fo list.fo

chrisg 2002/07/04 13:20:55 Modified:docs/examples/fo Tag: fop-0_20_2-maintain list.fo Log: changed list.fo to prevent a bug (text-align="end" in a list-item-label) Revision ChangesPath No revision No revision 1.6.4.3

RE: STATUS OF FOP ? the new re-engineered FOP?

ja, i know just look at this motherless freeking disclaimer, what a bunch of BS, sorry guys, there's nothing I can do about it, DD is one of those disclaimer mad places you know? -Original Message- From: Matthew L. Avizinis [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 04, 2002 5:41 PM

cvs commit: xml-fop CHANGES

chrisg 2002/07/04 08:48:03 Modified:.Tag: fop-0_20_2-maintain CHANGES Log: added missing CHANGES Revision ChangesPath No revision No revision 1.10.2.21 +5 -0 xml-fop/CHANGES Index: CHANGES =

RE: STATUS OF FOP ? the new re-engineered FOP?

Oh, come on now, this is just ridiculous.. > > > This message contains information intended solely for the addressee, > which is confidential or private in nature and subject to legal privilege. > If you are not the intended recipient, you may not peruse, use, > disseminate, distribute or copy

Re: STATUS OF FOP ? the new re-engineered FOP?

These efforts are still ongoing. There's no release of the re-engineered FOP, yet. It's not possible, yet, to say when this is going to be finished. But the good news is that you will be able to re-use your stuff. You will only have to adjust the way you call FOP. But that's something we're going

Re: [vote] removing BufferManager and XTTreeBuilder

Joerg Pietschmann schrieb: > Hello all, > there is some dead wood to cut: > - The BufferManager isn't used anymore, because it apparently > caused more harm than good (see Mark Lillywhite's comments) > +1 for removing all references and delete the files in fop/system +1 (after the release - whi

Re: STATUS OF FOP ? the new re-engineered FOP?

On Thu, 2002-07-04 at 11:24, [EMAIL PROTECTED] wrote: > Hi all, > > I used the maintenance release of FOP last year and I noticed that there is > now a new re-engineered version. How is it, and will i be able to re-use my > previous FOP stuff? There isn't a release of the re-engineered version.

Re: [vote] removing BufferManager and XTTreeBuilder

> there is some dead wood to cut: > - The BufferManager isn't used anymore, because it apparently > caused more harm than good (see Mark Lillywhite's comments) > +1 for removing all references and delete the files in fop/system +1 > - The XTFOTreeBuilder provides a SAX1 interface. It is not us

cvs commit: xml-fop/src/org/apache/fop/svg PDFGraphics2D.java PDFTextPainter.java

keiron 2002/07/04 07:08:20 Modified:src/org/apache/fop/area/inline Viewport.java src/org/apache/fop/fo/flow ExternalGraphic.java src/org/apache/fop/pdf PDFDocument.java PDFGState.java PDFResources.java PDFState.java s

[vote] removing BufferManager and XTTreeBuilder

Hello all, there is some dead wood to cut: - The BufferManager isn't used anymore, because it apparently caused more harm than good (see Mark Lillywhite's comments) +1 for removing all references and delete the files in fop/system - The XTFOTreeBuilder provides a SAX1 interface. It is not used

cvs commit: xml-fop/src/org/apache/fop/viewer/Images reload.gif

chrisg 2002/07/04 05:00:26 Modified:src/org/apache/fop/apps Tag: fop-0_20_2-maintain AWTStarter.java src/org/apache/fop/viewer Tag: fop-0_20_2-maintain PreviewDialog.java Added: src/org/apache/fop/viewer/Images Tag:

DO NOT REPLY [Bug 1063] - fop does not handle large fo files

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 10475] - FOP runs out of memory

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 10475] New: - FOP runs out of memory

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

STATUS OF FOP ? the new re-engineered FOP?

Hi all, I used the maintenance release of FOP last year and I noticed that there is now a new re-engineered version. How is it, and will i be able to re-use my previous FOP stuff? This message contains information intended solely for the addressee, which is confidential or private in nature and

Re: Line breaking and Hyphenation

These (and other) problems are precisely why certain areas have been redesigned. Wouldn't it be better to put the effort into getting the new code to work? On Wed, 2002-07-03 at 10:57, Joerg Pietschmann wrote: > I put a StringBuffer into FObjMixed to accumulate > consecutive addCharacters() even

cvs commit: xml-fop/src/org/apache/fop/image ImageFactory.java

keiron 2002/07/04 00:30:57 Modified:src/org/apache/fop/image ImageFactory.java Log: removed repeated string Revision ChangesPath 1.8 +1 -2 xml-fop/src/org/apache/fop/image/ImageFactory.java Index: ImageFactory.java =

cvs commit: xml-fop/src/org/apache/fop/svg PDFTextElementBridge.java

keiron 2002/07/04 00:30:02 Modified:src/org/apache/fop/svg PDFTextElementBridge.java Log: prevent npe Revision ChangesPath 1.8 +2 -2 xml-fop/src/org/apache/fop/svg/PDFTextElementBridge.java Index: PDFTextElementBridge.java =