DO NOT REPLY [Bug 6997] - Row-spanned row data breaks over a page within a column

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_bug

cvs commit: xml-fop/src/org/apache/fop/traits SpaceVal.java

keiron 2003/02/12 20:24:19 Modified:src/org/apache/fop/fo/flow Leader.java src/org/apache/fop/layoutmgr BlockContainerLayoutManager.java BlockLayoutManager.java BlockStackingLayoutManager.java BreakPo

Re: Another release candidate ...

> This sounds great, but I have one question. We've posted a bug report > (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16672) about the SVG > rendering in 0.20.4 and 0.20.5. Our SVG's in the rendered PDF > document(s) gets clipped. We're now using 0.20.1 and everything is fine > there. T

RE: Encryption

Jeremias (et al.), I have implemented the changes as prescribed and tested it with several fo files containing text and graphics. Everything looks good so far. I have two open issues: 1) I have implemented the encryption through the command line interface and renderOptions. Should it have been im

Re: Another release candidate ...

Christian Geisert wrote: Ok, in a perfect world the 0.20.5 release would have happend last year and we all were working on HEAD now but in reality we're still fixing bugs (which is ok as it will take some time till the first "redesign-relase") but nevertheless we should finally finish 0.20.5. So

Re: Another release candidate ...

Christian Geisert wrote: So I propose the following plan: Make another RC on february 17th and do the final 0.20.5 release on february the 28th (no delay except for very valid reasons) +1 J.Pietschmann - To unsubscribe, e-mai

DO NOT REPLY [Bug 17013] - fop aborts with NullPointerException / id on table-row

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 17013] New: - fop aborts with NullPointerException / id on table-row

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

Re: Another release candidate ...

Christian Geisert wrote: Ok, in a perfect world the 0.20.5 release would have happend last year and we all were working on HEAD now but in reality we're still fixing bugs (which is ok as it will take some time till the first "redesign-relase") but nevertheless we should finally finish 0.20.5. So

Another release candidate ...

Ok, in a perfect world the 0.20.5 release would have happend last year and we all were working on HEAD now but in reality we're still fixing bugs (which is ok as it will take some time till the first "redesign-relase") but nevertheless we should finally finish 0.20.5. So I propose the following pl

Re: FopServlet example!

Hi, Ive attached the Java class, (and included it at the bottom incase attachment fails to send). There are two methods, and they both require the HttpServletResponse. It provides options for either sending it the XML and XSL as files or strings. Ensure that you have copied the following jar

DO NOT REPLY [Bug 16999] New: - fo:retrieve-marker takes marker from wrong page

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 16996] - build.bat script fails with javac error.

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 16996] - build.bat script fails with javac error.

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 16996] - build.bat script fails with javac error.

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 16996] New: - build.bat script fails with javac error.

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

Errors using TTF from FreeFont project

Hello, I've tried to use TTF fonts from FreeFont project (http://savannah.nongnu.org/projects/freefont/) with FOP 0.20.5rc and FOP logs these errors: [ERROR] TrueType warning: Can't find fpgm table [ERROR] TrueType warning: Can't find prep table But created PDF file looks fine. What does these e

The best way to control page break

Hi mates, I'm now using FOP for 2 months, we really appreciate this way to automatically generate our catalogs here. I have to work those days on a new XSL:FO layout that must manage fine page break system. Is there a better way for handling that than using the XSL string-length() and sum() wit

Re: FopServlet example!

Thank you both. I have now implemented a class that takes two strings (xml-source and xsl-source and the servlet-response) and the class deals with converting this. If anyone would like a copy of this please let me know. Thanks again. Ghulam From: "J.Pietschmann" <[EMAIL PROTECTED]> Reply

RE: Throwing away code was: Re: cvs commit:

> I think that the reason resources are not forthcoming > is because of the barriers to entry that we have raised, > the largest being that, if you want to work on the code, > you really only get to work on the code that doesn't run. > For most people, that is a no starter. I think when the > trunk