Re: Merging jfor into FOP - what's the plan?

2001-11-26 Thread Keiron Liddle
Hi Bertrand, For the short term I think that (1) would be the thing to do but since there won't be a release of FOP for a while there may be no point doing anything for the short term. As for how it will eventually end up working with the rest of fop. Can you give us a quick rundown of what

DO NOT REPLY [Bug 5075] New: - problems with DOM input

2001-11-26 Thread bugzilla
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=5075. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 5075] - problems with DOM input

2001-11-26 Thread bugzilla
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=5075. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

RE: basic-link internal-destination

2001-11-26 Thread Suhail Rashid
the id has to be unique.. possibly ur assigning the same id at more than one location in your document.. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, November 26, 2001 12:15 PM To: [EMAIL PROTECTED] Subject: fo:basic-link internal-destination

RE: basic-link internal-destination

2001-11-26 Thread lpkhoo
Hello, Suhail Rashid the id is unique . Actaully in my whole document only have one basic-link and only one id. Do you have any idea or do u done before about internal-destination where the fo:basic-link internal-destination in one page and fo:block id in another page? hope you can help me.

DO NOT REPLY [Bug 5010] - Better error reporting needed

2001-11-26 Thread bugzilla
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=5010. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 5075] - problems with DOM input

2001-11-26 Thread bugzilla
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=5075. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 5075] - problems with DOM input

2001-11-26 Thread bugzilla
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=5075. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

RE: keep-with-next, orphans, widows

2001-11-26 Thread Michail Bikoulis
keep-with-next is implemented only for tables. Take a look at docs\html-docs\implemented.html under the FOP home directory to find out what is implemented. Regards, Mike -Original Message- From: Jörg Flotho [mailto:[EMAIL PROTECTED]] Sent: 26. november 2001 14:33 To: [EMAIL PROTECTED]

... and scripts

2001-11-26 Thread Peter B. West
I have added a script list from the first draft of the standard. Peter Peter B. West wrote: I have created a class LanguageFileReader and a config file xml-lang.xml to adrees the (slightly)dynamic nature of the 639/3166 codes. A modified Options class checks for languageConfigFileName in

Re: Font embedding in PostScript?

2001-11-26 Thread Jeremias Maerki
Well, if the font is embedded in the PDF, it gets embedded in to resulting PostScript file. If it's not, no embedding is done. I don't think you can have the fonts embedded in the PostScript when they aren't embedded in the PDF. Not sure, though. Maybe Ghostscript can do that. I've never tried.

RE: keep-with-next, orphans, widows

2001-11-26 Thread Savino, Matt C
It's my understanding, that right now keep-with-next is only implemented on the table-row element. What's more, you can only use it when you know you will not have any more rows than will fit on a page. Otherwise FOP goes into an endless loop. -Original Message- From: Jörg Flotho

DO NOT REPLY [Bug 5099] New: - fop gets stuck in infinite loop when table rows with keep-with-next that together, are larger than the current page

2001-11-26 Thread bugzilla
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=5099. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 5100] New: - Useless error message

2001-11-26 Thread bugzilla
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=5100. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

cvs commit: xml-fop/src/org/apache/fop/fo RecursiveCharIterator.java

2001-11-26 Thread klease
klease 01/11/26 13:11:06 Modified:src/org/apache/fop/fo RecursiveCharIterator.java Log: Fix a small bug in iterator Revision ChangesPath 1.2 +2 -0 xml-fop/src/org/apache/fop/fo/RecursiveCharIterator.java Index: RecursiveCharIterator.java

Bug in fo:basic-link

2001-11-26 Thread lpkhoo
Hello, I found a bug in fo:basic-link internal-destination where it can't do internal link for fop 0.20.1. During run fop0.20.1, if the document have more then one page and the fo:basic-link internal-destination in one page and fo:block id in another page then the fop were given me an error

HELP: PDF generation hangs

2001-11-26 Thread Vladimir Sneblic
Hi, I have a problem when I try to generate a PDF file from a FOP file that contains an SVG image. It doesn't matter if the image is inline or if it's stored as a separate file. My problem is that the PDF file gets generated but for some reason the java thread hangs, i.e. even though the work is

Re: Merging jfor into FOP - what's the plan?

2001-11-26 Thread Bertrand Delacretaz
Hi Keiron, If there is not going to be a FOP release in the next few weeks, I agree that a minimal integration does not make sense. Currently the jfor conversion is driven directly from SAX events, so the first thing that comes to mind is driving it from the FO tree. You're right that,