border-top and -bottom on table-rows
Hi, I'm trying to figure out how to do a border between rows of a table, but the borders are either not appearing or are being hidden by something else. What is the expected behaviour of a border-top or -bottom? The fo is like this... fo:table width=10cm table-layout=fixed fo:table-column column-width=5cm/ fo:table-column column-width=5cm/ fo:table-body fo:table-row background-color=rgb(90%, 50%, 40%) border-top=solid 1px black border-bottom=solid 1px black fo:table-cellfo:blockTest/fo:block/fo:table-cell fo:table-cellfo:blockTest/fo:block/fo:table-cell /fo:table-row /fo:table-body /fo:table ... and at least here there are no borders on the table row. As a secondary question, when will percentages be supported in table (and block) widths? At least in the version of fop that I'm using, there's no support for it. And finally (I promise) - is there a definitive document anywhere detailing what bits of the xsl standard fop supports, and what bits it doesn't? Cheers, Dave. -- David Neary Phenix Engineering 110 ave Jean Jaures, 69007 Lyon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FOP output streaming
Hi We develop a client application which realizes printing through PDF rendering. Since memory on the clients is limited and the users can print hundreds of pages, the memory complexity of the PDF renderer must not depend on the number of pages printed. But up to the latest FOP release 0.20.4 exactly this is the case, if you use a single page sequence. FOP runs out of memory after 10-40 pages. The page sequences cannot be splitted without degrading the quality of the printing. Now I've seen the following point on the changes page on the website: Implemented on-the-fly stream output (less buffering leads to decreased memory usage and increased speed) Does this solve this problem? In which version is it implemented? I tried 0.20.5rc2. The situation is much better there, but not yet solved. Daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: border-top and -bottom on table-rows
From: David Neary [EMAIL PROTECTED] I'm trying to figure out how to do a border between rows of a table, but the borders are either not appearing or are being hidden by something else. What is the expected behaviour of a border-top or -bottom? The broders on rows and columns dont work for me either. I found that you have to specify the borders for each individual cell. As a secondary question, when will percentages be supported in table (and block) widths? At least in the version of fop that I'm using, there's no support for it. You can mimick percentage for the column widths as shown below; fo:table-column width=proportional-column-width(1)/ 25% fo:table-column width=proportional-column-width(2)/ 50% fo:table-column width=proportional-column-width(1)/ 25% And finally (I promise) - is there a definitive document anywhere detailing what bits of the xsl standard fop supports, and what bits it doesn't? please see http://xml.apache.org/fop/compliance.html _ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Png image
Works fine here. Have you tried another PNG from a different source? In case you use the source distribution: did you do a full rebuild of FOP with Jimi included? On 14.04.2003 17:33:34 vikram.x.kondadasula wrote: I am using a gif ,as background image.It works finebut if I use a png image it does not work, even after including the jimi-1.0.jar file.Can somebody point me in the right direction. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
xsl:import error with new jaxp and fop 0.20.5rc2
I just upgraded to fop 0.20.5rc2 and switched to jaxp (newest version) and now all of my stylesheets transformations fail with the following: javax.xml.transform.TransformerException: xsl:import is not allowed in this position in the stylesheet! at org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.java:951) at org.apache.xalan.processor.StylesheetHandler.getProcessorFor(StylesheetHandler.java:428) at org.apache.xalan.processor.StylesheetHandler.startElement(StylesheetHandler.java:662) at org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1371) at org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidator.java:840) at org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1853) at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1234) at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381) at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:948) at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:972) at org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:788) I think it has something to do with the jar files - can someone please send me a jar file version list for this version of FOP and/or any suggestions on how to fix this. Thanks, Lou - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP output streaming
Please check the following URL for ideas to improve the situation. http://xml.apache.org/fop/faq.html#OutOfMemoryException On 15.04.2003 12:30:17 Daniel Tschan wrote: We develop a client application which realizes printing through PDF rendering. Since memory on the clients is limited and the users can print hundreds of pages, the memory complexity of the PDF renderer must not depend on the number of pages printed. But up to the latest FOP release 0.20.4 exactly this is the case, if you use a single page sequence. FOP runs out of memory after 10-40 pages. The page sequences cannot be splitted without degrading the quality of the printing. Now I've seen the following point on the changes page on the website: Implemented on-the-fly stream output (less buffering leads to decreased memory usage and increased speed) This only works as long as pages can be fully resolved. As soon as you have a page x of y on each page the first page can only be output when the last page is known. Changing that to page x only can help solve this problem. Other references play into this as well. Does this solve this problem? In which version is it implemented? I tried 0.20.5rc2. The situation is much better there, but not yet solved. The redesign contains some code that allows temporary serialization of pages until they are ready to be finalized. This will slow down the process but reduce memory usage. The problem is that a release from the redesign will still take a while so you're stuck with the above techniques to reduce memory usage until we have the redesign ready to take over. I hope that helps a bit. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: error converting SVG to PDF
Batik 1.5 beta5 has the PDF transcoder included. As an alternative you can try to rename fop.jar to pdf-transcoder.jar so the classpath specified inside batik-rasterizer.jar picks up FOP at all. The problem you have is that fop.jar doesn't get loaded into the classpath. The other possibility is to explicitly specify the classpath using -cp or -classpath instead of using -jar. And last but not least: The PDF transcoder you get when downloading the HEAD branch from CVS (or from a CVS snapshot) will give you an improved implementation of the PDF transcoder. We'll soon do a separate release of that code. On 15.04.2003 16:46:18 Gary Marshall-Stevens wrote: Can anyone help with this issue: I have batik-1.1.1 installed and fop-0.20.4 both binaries. I am running the following at the command line: C:\FOP\batik-1.1.1java -jar batik-rasterizer.jar -m application/pdf samples/batikFX.svg this is the error I receive: Error while converting files: Error: cannot access transcoder for image of type application/pdf Will installing the src instead of binaries fix this ? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
problem with page sequence
Hai, The following page sequence genertes two pages instead of one.Could anybody tell me why this happens. fo:page-sequence-master master-name=run1 fo:repeatable-page-master-reference master-reference =headersimpleA4 page-position=first maximum-repeats=1/ /fo:page-sequence-master fo:page-sequence master-reference=run1 fo:flow flow-name=xsl-region-body fo:blockTestPage /fo:block /fo:flow /fo:page-sequence Thanks Vikram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP output streaming
Thanks for your fast reply. Please check the following URL for ideas to improve the situation. http://xml.apache.org/fop/faq.html#OutOfMemoryException Thanks, but we already did follow all this points. Memory usage is still depending on the number of pages. This only works as long as pages can be fully resolved. As soon as you have a page x of y on each page the first page can only be output when the last page is known. Changing that to page x only can help solve this problem. Other references play into this as well. Our pages contain no references at all. So theoretically a page can be finalized after a new one has begun. The redesign contains some code that allows temporary serialization of pages until they are ready to be finalized. What prevents a page from beeing finalized if there are no references in it? This will slow down the process but reduce memory usage. The problem is that a release from the redesign will still take a while so you're stuck with the above techniques to reduce memory usage until we have the redesign ready to take over. On the other hand less memory usage can result in increased speed. Can you give us some hints so that we can try to find a quick and dirty solution for now? The reasons that prevent the pages from beeing finalized at once may not apply in all cases. Perhaps we can make some optimizations based on our specific application. Daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem with page sequence
[EMAIL PROTECTED] wrote: The following page sequence genertes two pages instead of one. Are you sure? This should only happen if another page sequence follows. Also read http://xml.apache.org/fop/faq.html#blank-page-between-page-sequences J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Help with unicode characters
Hello: I just processed an xsl:fo with FOP and got this message: An invalid xml character unicode: 0x1A6821 ... Try as I might, I can't find a unicode character that matches that number, nor was I able to find FOPs explanation of this message. Can anyone tell me how to interpret that message and find a matching unicode character? Thanks Jon Steeves Technical Communications (604) 415-6053 ext. 2139 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
