RE: FOP 0.93: Java Heap Space OutOfMemory
Seems there was not enough space on harddisk for generating the PDF-Output with FOP 0.93. Is there a option for FOP to display how many space on harddisk is needed while generating a PDF? This time over 200 MB were needed by FOP to generate a less than 2 MB big PDF-File. Regards, Kerstin --- [EMAIL PROTECTED] schrieb: While generating a PDF from XML+XSL using FOP 0.93, FOP stops with Exception in thread main java.lang.OutOfMemoryError: Java heap space. Are their any limitations set in FOP or this is just a problem of to few system memory? The generated PDF have more than 71 pages. - Besseren Schutz gegen Spam - jetzt bei dem neuen Yahoo! Mail . __ Die besten Tipps und Tricks fürs Grillen. BE A BETTER GRILLMEISTER! www.yahoo.de/clever - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP from TRUNK: Hyphenation LineBreak-Problem???
Hi Manuel, thanks for the fast fix. I update my fop-trunk-folder and tried to build fop with ant again. While building fop ant displays following message: apache-ant-1.6.5/bin/ant: line 80: uname: command not found Now trying to generate a pdf with FOP FOP just display this lines: ./FOP_TRUNK/fop: line 79: uname: command not found ./FOP_TRUNK/fop: line 91: basename: command not found ./FOP_TRUNK/fop: line 104: dirname: command not found Exception in thread main java.lang.NoClassDefFoundError: org/apache/fop/cli/Main Did I something wrong because I tried to build FOP again with ANT??? Or is it just another mistake?? Best Regards, Leeloo PS: Yes, it's right Betrie-bsablauf is not separated correctly. Manuel Mall [EMAIL PROTECTED] schrieb: On Thursday 11 January 2007 17:55, Manuel Mall wrote: On Thursday 11 January 2007 14:00, malm wrote: leeloo5e79-docbook wrote: It could be that the new UAX#14 line breaking introduced after 0.93 in late December is causing this. Can you please provide a full working testcase fo exhibiting the problem (if possible attached please not inlined with the message). Thanks Don't worry to send something else. The problem is caused by some interaction between the new UAX#14 linebreaking and hyphenation when explicit hyphens like in 'IT-System' are involved. I am looking at a fix. Fix committed: http://svn.apache.org/viewvc?view=revrev=495175 BTW, looks like the German hyphenation pattern have some issues. To hyphenate 'Betriebsablauf' as 'Betrie-bsablauf' appears to be a bit unconventional. Manuel Manuel Manuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Was Sie schon immer wissen wollten aber nie zu Fragen trauten? Yahoo! Clever hilft Ihnen.
Re: FOP from TRUNK: Hyphenation LineBreak-Problem???
Hi Manuel, maybe this was the problem. I tried again and now all was build fine. Maybe something wrong in my SSH-Client. The head of the table looks fine now :-))) Thanks a lot. Best Regards, Leeloo Manuel Mall [EMAIL PROTECTED] schrieb: On Thursday 11 January 2007 21:15, [EMAIL PROTECTED] wrote: Hi Manuel, thanks for the fast fix. I update my fop-trunk-folder and tried to build fop with ant again. While building fop ant displays following message: apache-ant-1.6.5/bin/ant: line 80: uname: command not found Now trying to generate a pdf with FOP FOP just display this lines: ./FOP_TRUNK/fop: line 79: uname: command not found ./FOP_TRUNK/fop: line 91: basename: command not found ./FOP_TRUNK/fop: line 104: dirname: command not found Exception in thread main java.lang.NoClassDefFoundError: org/apache/fop/cli/Main This looks like a problem with your Unix path (or are you using cygwin?) because uname, dirname, basename are all Unix commands used in the shell script to start fop. Also check the line endings in the shell script files. I think the Unix shells don't like script files with Windows cr/lf end of lines. Manuel Did I something wrong because I tried to build FOP again with ANT??? Or is it just another mistake?? Best Regards, Leeloo PS: Yes, it's right Betrie-bsablauf is not separated correctly. Manuel Mall schrieb: On Thursday 11 January 2007 17:55, Manuel Mall wrote: On Thursday 11 January 2007 14:00, malm wrote: leeloo5e79-docbook wrote: It could be that the new UAX#14 line breaking introduced after 0.93 in late December is causing this. Can you please provide a full working testcase fo exhibiting the problem (if possible attached please not inlined with the message). Thanks Don't worry to send something else. The problem is caused by some interaction between the new UAX#14 linebreaking and hyphenation when explicit hyphens like in 'IT-System' are involved. I am looking at a fix. Fix committed: http://svn.apache.org/viewvc?view=revrev=495175 BTW, looks like the German hyphenation pattern have some issues. To hyphenate 'Betriebsablauf' as 'Betrie-bsablauf' appears to be a bit unconventional. Manuel Manuel Manuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Was Sie schon immer wissen wollten aber nie zu Fragen trauten? Yahoo! Clever ans wers.yahoo.com hilft Ihnen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - NEU: Fragen stellen - Wissen, Meinungen und Erfahrungen teilen. Jetzt auf Yahoo! Clever.
Re: Update from Trunk Errors with FOP
Hi Jeremias, thanks a lot for your answers :-) Update form Trunk works very fine now after setting the needed proxy in the TortoiseSVN. The First Download and Update from Trunk works without the Proxy-Settings. Maybe strange but never mind now. My PDF-Output looks good at this moment. But maybe in further versions of FOP this warnings are no longer warnings but errors and no output are generated. Maybe I have a deeper look at the attributes to make a more decent FO-File for FOP. Best Regards, Leeloo Jeremias Maerki [EMAIL PROTECTED] schrieb: On 04.01.2007 15:33:45 leeloo5e79-docbook wrote: I still have a lot of errors using FOP in 0.92beta or better from Trunk I think. Since a while I can't update from Trunk: TortoiseSVN said: Error: PROPFIND request failed on '/repos/asf/xmlgraphics/fop/trunk' Error: PROPFIND of '/repos/asf/xmlgraphics/fop/trunk': could not connect to server (http://svn.apache.org) Anything wrong with the server? Last year it worked fine. The server could have been down for some reason. Just retry later. Or if you're behind a proxy you may have to use https instead of http. First message I got while converting a XML to PDF is org.apache.fop.fo.flow.TableColumn bind WARNING: table-layout=fixed and column-width unspecified = falling back to proportional-column-width(1) Deleting table-layout=fixed because it is not supported (http://xmlgraphics.apache.org/fop/compliance.html#fo-property-table-layout), produces another error/warning: Nono. You'll have to leave table-layout=fixed but you should specify column-widths. But this warning can safely be ignored if you get the expected output. WARNING: Warning(Unknown location): fo:table, table-layout=auto is currently not supported by FOP 04.01.2007 11:11:34 org.apache.fop.fo.PropertyList convertAttributeToProperty FATAL: Ignoring property: column-width=proportional-column-width(1) (proportional-column-width() function may only be used when fo:table has table-layout=fixed.; property:'column-width') What does this mean? Using column-with in fo:table which is supported by FOP (http://xmlgraphics.apache.org/fop/compliance.html#fo-property-column-width) without table-layout=fixed produces an error. And using it with table-layout=fixed because this is not support produces also an error. Somebody is understanding this? And table-layout=auto are also not supported. Not an error, a warning. table-layout=auto is indeed not implemented, yet, but fixed is. We're just nitpickers concerning your not specifying column-widths in this case. :-) Next error seems to mean that the first row of a table is taller than the row should be: org.apache.fop.layoutmgr.table.TableContentLayoutManager createElementsForRowGroup WARNING: The contents of row 1 are taller than they should be (there is a block-progression-dimension or height constraint on the indicated row). Due to its contents the row grows to 76820 millipoints, but the row shouldn't get any taller than MinOptMax[min=opt=max=14000] millipoints. (fo:table-row, no context info available) For some tables I specified a column-width, maybe this could be the error. But I do not specified the widths in millipoints but used proportional measure. So, there should be no taller row than they should be, or !? After the next rows the error causes with FOP in the FO-File I guess I should write an FAQ entry about that. You specify height on the row. By using height you implicitely set block-progression-dimension.minimum, block-progression-dimension.optimum and block-progression-dimension.maximum to the same value (see MinOptMax[min=opt=max=14000] above). Now, if your content gets larger than 14pt (76.820pt in your case) in vertical direction the content actually violates a constraint (maximum=14pt). The warning message actually says pretty much that. You probably just didn't know that height maps to block-progression-dimension. height is only a corresponding property. Again, it's a warning, not an error, although strictly speaking, it is a layout error. Depends on your nitpicking level. :-) To get rid of the warning the usual work-around is to use block-progression-dimension.minimum=14pt instead of height=14pt. This allows the table-row to grow as necessary while maintaining a minimum height. Another error seems to have a problem with the PageBreakingAlgorithm: org.apache.fop.layoutmgr.PageBreakingAlgorithm updateData2 WARNING: Part/page 1 overflows the available area in block-progression dimension. (fo:static-content, no context info available) To engender a PageBreak, I'm using . For the time being last error: org.apache.fop.layoutmgr.StaticContentLayoutManager doLayout WARNING: static-content overflows the available area. (fo:static-content, no context info available) Similar problem as with your table-row. Your content is larger than the available area you defined for your header or footer. Set a background-color
FOP from TRUNK: Hyphenation LineBreak-Problem???
Hello List, after the update of FOP from TRUNK today, I've got a WARNING while generating a PDF-Output. org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2 WARNUNG: Line 1 of a paragraph overflows the available area. (fo:block, Aggregierte Ausfallzeit IT-System) org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2 WARNUNG: Line 2 of a paragraph overflows the available area. (fo:block, IT-Anwendung, die IT-System benutzt) This time this warning has effects on the real PDF-Output. It looks not very nice. The table-cell in fo looks like this: fo:table-cell padding-left=2pt padding-right=2pt padding-top=2pt padding-bottom=2pt border-bottom-width=0.5pt border-bottom-style=solid border-bottom-color=black border-right-width=0.5pt border-right-style=solid border-right-color=black text-align=centerfo:block font-weight=boldAggregierte Ausfallzeit IT-System/fo:block/fo:table-cell The table cell in PDF-Output is broken like this: Aggre- gier- te Aus- fallzeit IT-System and this IT-Anwen- dung, die IT-System benutzt After correct hyphenation then on last or second line there is no normal break or another hyphenation. And so the available area is overflowing from this. In the same table I have also long text which are separated and nothing is overflowing. Using FOP 0.93 or the TRUNK-Version from beginning of december 2006 everything is fine. Any suggestions? Best Regards, Leeloo - Der neue Internet Explorer 7 in deutscher Ausführung ist da!
Update from Trunk Errors with FOP
I still have a lot of errors using FOP in 0.92beta or better from Trunk I think. Since a while I can't update from Trunk: TortoiseSVN said: Error: PROPFIND request failed on '/repos/asf/xmlgraphics/fop/trunk' Error: PROPFIND of '/repos/asf/xmlgraphics/fop/trunk': could not connect to server (http://svn.apache.org) Anything wrong with the server? Last year it worked fine. First message I got while converting a XML to PDF is org.apache.fop.fo.flow.TableColumn bind WARNING: table-layout=fixed and column-width unspecified = falling back to proportional-column-width(1) Deleting table-layout=fixed because it is not supported (http://xmlgraphics.apache.org/fop/compliance.html#fo-property-table-layout), produces another error/warning: WARNING: Warning(Unknown location): fo:table, table-layout=auto is currently not supported by FOP 04.01.2007 11:11:34 org.apache.fop.fo.PropertyList convertAttributeToProperty FATAL: Ignoring property: column-width=proportional-column-width(1) (proportional-column-width() function may only be used when fo:table has table-layout=fixed.; property:'column-width') What does this mean? Using column-with in fo:table which is supported by FOP (http://xmlgraphics.apache.org/fop/compliance.html#fo-property-column-width) without table-layout=fixed produces an error. And using it with table-layout=fixed because this is not support produces also an error. Somebody is understanding this? And table-layout=auto are also not supported. Next error seems to mean that the first row of a table is taller than the row should be: org.apache.fop.layoutmgr.table.TableContentLayoutManager createElementsForRowGroup WARNING: The contents of row 1 are taller than they should be (there is a block-progression-dimension or height constraint on the indicated row). Due to its contents the row grows to 76820 millipoints, but the row shouldn't get any taller than MinOptMax[min=opt=max=14000] millipoints. (fo:table-row, no context info available) For some tables I specified a column-width, maybe this could be the error. But I do not specified the widths in millipoints but used proportional measure. So, there should be no taller row than they should be, or !? After the next rows the error causes with FOP in the FO-File fo:table-column column-number=1 column-width=proportional-column-width(1)/ fo:table-column column-number=2 column-width=proportional-column-width(0)/ fo:table-column column-number=3 column-width=proportional-column-width(1)/ fo:table-bodyfo:table-row height=14pt Another error seems to have a problem with the PageBreakingAlgorithm: org.apache.fop.layoutmgr.PageBreakingAlgorithm updateData2 WARNING: Part/page 1 overflows the available area in block-progression dimension. (fo:static-content, no context info available) To engender a PageBreak, I'm using fo:block break-after=page/. For the time being last error: org.apache.fop.layoutmgr.StaticContentLayoutManager doLayout WARNING: static-content overflows the available area. (fo:static-content, no context info available) While writing this rows I found out, that this error occurs in the following row of the generated FO-File: fo:page-sequence xmlns:axf=http://www.antennahouse.com/names/XSL/Extensions; master-reference=body hyphenate=true language=de format=1 initial-page-number=1 force-page-count=no-force hyphenation-character=- hyphenation-push-character-count=2 hyphenation-remain-character-count=3 fo:static-content flow-name=xsl-region-before-first fo:block font-family=Arial, Helvetica, sans-serif,Symbol,ZapfDingbats margin-left=0pt fo:table width=100% table-layout=fixed fo:table-column column-number=1 column-width=proportional-column-width(1)/ fo:table-column column-number=2 column-width=proportional-column-width(0)/ fo:table-column column-number=3 column-width=proportional-column-width(1)/ fo:table-body ... I don't know why this error occurs. This XSL:FO is generated from the Docbook-XSL I think. Maybe these are all trivial errors/warings - However PDF is generated. But it let being to suspicious. Has anybody some explanations? Or these are just faults whereof is still working? Thanks a lot! Best Regards, Leeloo __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
Re: fo:table-row is missing child elements
Hi Glen, running FOP 0.92beta with the option -r relaxed/less strict validation (where available) now generates a PDF without the error described below :-))) Thanks and happy new year. Best Regards, Leeloo Glen Mazza [EMAIL PROTECTED] schrieb: [EMAIL PROTECTED] escribió: Trying to convert an FO-File which was generated by FOP 0.92beta to an PDF just stopped with following Error Message: javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: file:///test/test.fo:1:43655: Error(1/43655): fo:table-row is missing child elements. Required Content Model: (table-cell+) Process of elimination is probably best here: keep minimizing your FO file until you identify the element causing the error to occur. There is also an option I believe in FOP 0.93 to run in non-strict validation mode, which would I believe would accept the situation that is occurring for you. I can't find any fo:table-row in FO-File which missed a fo:table-cell. I think everything is alright. Using FOP 0.20.5 converting the XML to PDF - it works fine. The new FOP raises an error by default, as protection in case you goofed up your XSLT template calls and ended up creating no cells where you actually wanted some. This way erroneously created invoices with no rows, for example, won't end up going out to the customer, or if you create a 250 page document you don't have to manually read each page just to make sure every table has the rows you intended. Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
Re: fo:table-row is missing child elements
Yes, it is the Docbook-XSL-Stylesheet 1.71.1 which causes this error. But strange to say using -r-mode a xml-file is created by FOP with the Docbook-XSL very well another one using the same Docbook-XSL and -r-mode causes the fo:table-row is missing child elements-error. It's all very confusing me. Regards, Leeloo Glen Mazza [EMAIL PROTECTED] schrieb: Hmmm...judging from your email address, I hope it is not a docbook stylesheet that is requiring you to run in -r mode. I would send a bug report to the OASIS docbook team if it is. Glen [EMAIL PROTECTED] wrote: Hi Glen, running FOP 0.92beta with the option -r relaxed/less strict validation (where available) now generates a PDF without the error described below :-))) Thanks and happy new year. Best Regards, Leeloo */Glen Mazza /* schrieb: [EMAIL PROTECTED] escribió: Trying to convert an FO-File which was generated by FOP 0.92beta to an PDF just stopped with following Error Message: javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: file:///test/test.fo:1:43655: Error(1/43655): fo:table-row is missing child elements. Required Content Model: (table-cell+) Process of elimination is probably best here: keep minimizing your FO file until you identify the element causing the error to occur. There is also an option I believe in FOP 0.93 to run in non-strict validation mode, which would I believe would accept the situation that is occurring for you. I can't find any fo:table-row in FO-File which missed a fo:table-cell. I think everything is alright. Using FOP 0.20.5 converting the XML to PDF - it works fine. The new FOP raises an error by default, as protection in case you goofed up your XSLT template calls and ended up creating no cells where you actually wanted some. This way erroneously created invoices with no rows, for example, won't end up going out to the customer, or if you create a 250 page document you don't have to manually read each page just to make sure every table has the rows you intended. Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
fo:table-row is missing child elements
Trying to convert an FO-File which was generated by FOP 0.92beta to an PDF just stopped with following Error Message: javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: file:///test/test.fo:1:43655: Error(1/43655): fo:table-row is missing child elements. Required Content Model: (table-cell+) I can't find any fo:table-row in FO-File which missed a fo:table-cell. I think everything is alright. Using FOP 0.20.5 converting the XML to PDF - it works fine. Trying to convert the XML directly to PDF using FOP 0.92beta, I got some additional WARNINGS: Mismatch: table-row (http://www.w3.org/1999/XSL/Format) vs. block (http://www.w3.org/1999/XSL/Format) Mismatch: table-row (http://www.w3.org/1999/XSL/Format) vs. flow (http://www.w3.org/1999/XSL/Format) Mismatch: table-row (http://www.w3.org/1999/XSL/Format) vs. page-sequence (http://www.w3.org/1999/XSL/Format) Mismatch: table-row (http://www.w3.org/1999/XSL/Format) vs. root (http://www.w3.org/1999/XSL/Format) Any suggestions? Best regards, Leeloo - Yahoo! Messenger - kostenlos* mit Familie und Freunden von PC zu PC telefonieren.
FOPException: No element found for Namespace URI:
On Wednesday this week I downloaded the actual files from FOP Trunk and compiled FOP using ANT. Now I'm trying to convert an XML-File to PDF or RTF with FOP but this occurs still this Error: org.apache.fop.apps.FOPException: Error(Unknown location): No element mapping definition found for (Namespace URI: http://xml.apache.org/fop/extensions;, Local Name: destination) If I create first ein FO-File with xsltproc and then trying to generate an RTF, this error ocurrs: org.apache.fop.apps.FOPException: file:///root/FOP/test.fo:2:28782: Error(2/28782): No element mapping definition found for (Namespace URI: http://xml.apache.org/fop/extensions;, Local Name: destination) In FO-File on line 2 and at character 28782 I found this: fox:destination internal-destination=id2508829/ ^ = character 28782 Using FOP 0.20.5 converting the same XML- and FO-File to PDF works fine. Using the example files at directory examples converting it to rtf works fine with FOP 0.92. Best Regards, Leeloo - Besseren Schutz gegen Spam - jetzt bei dem neuen Yahoo! Mail .
FOPException: No element found for Namespace URI:
On Wednesday this week I downloaded the actual files from FOP Trunk and compiled FOP using ANT. Now I'm trying to convert an XML-File to PDF or RTF with FOP but this occurs still this Error: org.apache.fop.apps.FOPException: Error(Unknown location): No element mapping definition found for (Namespace URI: http://xml.apache.org/fop/extensions;, Local Name: destination) If I create first ein FO-File with xsltproc and then trying to generate an RTF, this error ocurrs: org.apache.fop.apps.FOPException: file:///root/FOP/test.fo:2:28782: Error(2/28782): No element mapping definition found for (Namespace URI: http://xml.apache.org/fop/extensions;, Local Name: destination) In FO-File on line 2 and at character 28782 I found this: fox:destination internal-destination=id2508829/ ^ = character 28782 Using FOP 0.20.5 converting the same XML- and FO-File to PDF works fine. Using the example files at directory examples converting it to rtf works fine with FOP 0.92. Best Regards, Leeloo - Was Sie schon immer wissen wollten aber nie zu Fragen trauten? Yahoo! Clever hilft Ihnen.
