DO NOT REPLY [Bug 10100] New: - Blank lines when render to TEXT

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

Re: DO NOT REPLY [Bug 10031] - FOP error handling: return codes not set

Hi Jörg Yes, you should. :-) But I can't imagine that's the problem, because the message is relayed by CVS not by manually posting to this list, right? Has anybody received the CVS message from Jörg's change. I didn't. Maybe it's still somewhere in a moderator queue? That was the case when I

Re: test cases

Hi Jörg I think there is one: test. Keiron, was that you who created it in the first place? I must admit that I've never looked into this directory, yet. Does the stuff in there work? I've accumulated quit a few testcases from the bugzilla bug reports. Some are working now, some still

Re: Using bugzilla

I agree with what both of you said. BugZilla may not be perfect but it is a good enough tool for what Peter proposes. Patches tend to get forgotten if posted on the mailing list and not immediately committed. Todo lists are relatively hard to maintain in CVS. So, I'm all for using BugZilla more

Re: test cases

Jeremias Maerki wrote: I think there is one: test. Keiron, was that you who created it in the first place? I must admit that I've never looked into this directory, yet. Does the stuff in there work? Ah, yes. There is also a docs/examples/tests which is empty and is used to hold the results

Re: test cases

The testing as described here: http://xml.apache.org/fop/testing.html that is capable of running the w3c testsuite (and getting lots of errors etc.). This is only really about testing the layout. It sort of works but is possibly a bit early for these type of tests. I can see a need for other

FOP in the forrest

Hi, In order to improve the information, process and updating I suggest we start using better document systems. Forrest is the first thing that will help us here. With a supplement to the sitemap (not sure how to do this) we can also display FOP better. We can have a real examples page, show

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

keiron 2002/06/21 07:03:42 Modified:src/org/apache/fop/fo UnknownXMLObj.java src/org/apache/fop/render/awt AWTRenderer.java src/org/apache/fop/render/pcl PCLRenderer.java src/org/apache/fop/render/ps PSRenderer.java

[GUMP] Build Failure - xml-fop

This email is autogenerated from the output from: http://jakarta.apache.org/builds/gump/2002-06-21/xml-fop.html Buildfile: build.xml init-avail: init-filters-xalan2: [copy] Copying 1

DO NOT REPLY [Bug 6305] - Using fo:table-and-caption results in empty output

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

DO NOT REPLY [Bug 6537] - Table is missing in the generated PDF

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

DO NOT REPLY [Bug 2987] - Large graphics put FOP 0.19 into an infinite loop

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

DO NOT REPLY [Bug 3475] - Large images cause PDF generation to run out of memory

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

DO NOT REPLY [Bug 4348] - FOP has no mechanism to extend protocols

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

DO NOT REPLY [Bug 4670] - Entity Resolver for Images

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

DO NOT REPLY [Bug 6647] - external-graphic and configuration baseDir

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

DO NOT REPLY [Bug 4670] - Entity Resolver for Images

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

cvs commit: xml-fop/test/resources/fop/svg images.fo images.svg logo.jpg paints.svg transparency.svg link.svg text.svg

keiron 2002/06/21 08:17:37 Modified:test/resources/fop/svg link.svg text.svg Added: test/resources/fop/svg images.fo images.svg logo.jpg paints.svg transparency.svg Log: more svg tests with transparency, patterns and images Revision Changes

cvs commit: xml-fop/src/org/apache/fop/datatypes Slash.java

pbwest 2002/06/21 08:44:03 Added: src/org/apache/fop/datatypes Tag: FOP_0-20-0_Alt-Design Slash.java Log: Type to accommodate slash in size/height pair of font shorthand. Revision ChangesPath No revision No

Re: FOP in the forrest

Keiron Liddle schrieb: Hi, In order to improve the information, process and updating I suggest we start using better document systems. Forrest is the first thing that will help us here. With a supplement to the sitemap (not sure how to do this) we can also display FOP better. We can have

Re: [ANNOUNCEMENT] FOP 0.20.4 Release Candidate available

Martin Peina schrieb: [..] It works fine, just two things: 1) If baseDir is set for example to /opt/fop, FOP doesn't add / at the end of baseDir as other systems commonly does, so you can start use path for fonts like this: font

DO NOT REPLY [Bug 10100] - Blank lines when render to TEXT

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

Re: FOP in the forrest

Christian Geisert wrote: Keiron Liddle schrieb: Any questions, comments? I'm already adapting the docs to the forrest 1.1 DTDs There are some issues with the (old) documentation for the maintenance branch which I will bring up in an extra mail. Are they different from HEAD? J.Pietschmann

cvs commit: xml-fop/docs/design/alt.design intro.xml

pbwest 2002/06/21 23:07:51 Added: docs/design/alt.design intro.xml Log: Intro and index Revision ChangesPath 1.1 xml-fop/docs/design/alt.design/intro.xml Index: intro.xml ===

cvs commit: xml-fop/docs/design/alt.design book.xml

pbwest 2002/06/21 23:10:16 Modified:docs/design/alt.design book.xml Log: Added intro.xml as index Revision ChangesPath 1.5 +2 -1 xml-fop/docs/design/alt.design/book.xml Index: book.xml

cvs commit: xml-fop/docs/xml-docs/fop news.xml

pbwest 2002/06/21 23:12:14 Modified:docs/xml-docs/fop news.xml Log: Added rc4 news Revision ChangesPath 1.2 +50 -11xml-fop/docs/xml-docs/fop/news.xml Index: news.xml === RCS file: