Re: RTF output
On Oct 22, 2005, at 15:01, Glen Mazza wrote: I wonder if setting the margins on the fo:region-body (instead of the fo:external-graphic) would also have solved this. The example you gave had an empty fo:region-body/ without dimensions, but you may have been just abbreviating the sample by removing those dimensions. I doubt it, since many of our own layout-engine testcases have similar, minimal page-masters. If this were a problem, it would have surfaced much sooner... In the meantime, I've pinpointed the culprits. Seems it's the two calls one lines 952 and 955 in RTFHandler. These should first check whether the respective property has an enum value of auto instead of assuming that an explicit dimension will always be available, but what exactly should happen in case either value is auto, I'm not sure about that. I'd say the values of content-height and content- width should also be checked, and subsequently, the total bpd/ipd of the area containing the graphic can be inferred from its original size (?) Tony Morris escribió: Thanks, by explicitly setting a width and height, the problem disappeared - it only occurred for the RTF renderer (though I only tried the PDF one as well). The sizes themselves seem to be a tad obscure though. Tony, can you be a bit more precise as to what you mean by this last sentence? All I know is that, in FOP Trunk, with 'height' and 'width' you only specify the dimension of the area. Use them in combination with 'content-height' and 'content-width' to get appropriate results. HTH! Greetz, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with overlapping regions
Ok, it looks like it has to do with the nested tables. If you exchange the template for Offer_letter with the version I post below the overlap disappears and the last paragraph is broken over to the next page. It's probably a bug with accumulating height on a page when nested tables are involved. xsl:template match=Offer_letter fo:block fo:block xsl:apply-templates select=Address / /fo:block fo:block padding-top=2cm xsl:apply-templates select=ReferenceTo / /fo:block fo:block padding-top=1.5cm xsl:apply-templates select=Subject / /fo:block fo:block padding-top=0.5cm padding-bottom=2cm xsl:apply-templates select=ApplicationVersion / /fo:block fo:block xsl:apply-templates select=AllPositions / /fo:block fo:block padding-top=0.5cm xsl:apply-templates select=Amount / /fo:block fo:block padding-top=1cm xsl:apply-templates select=AdditionalInformations / /fo:block /fo:block /xsl:template On 24.10.2005 10:21:08 Timo Haberkern wrote: Hello again, thanks for reply. Sorry for the missing information. I'm using the version 0.20.5 of FOP. You can find a complete package for testing under: http://www.emedia-office.de/fop/fop_forum.zip It contains the generated PDF with the problem on the last site, the xml data file and the XSL file i use to convert Please help :-) Timo Jeremias Maerki wrote: The only weird thing I can see here is the extent property on the second region-body. This property doesn't apply to region-body. BTW, it would be much more fun to reproduce your problem if you posted a complete FO file and stated the FOP version you are using. :-) On 21.10.2005 13:47:56 Timo Haberkern wrote: Hello FOP List, i have a problem with overlapping regions. I have content of the region-body that overlapps content from region-after. You can see it on the screenshot: http://www.emedia-office.de/fop/overlapping.png i have defined my page as follows: fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=First-Page page-height=29.7cm page-width=21cm fo:region-body margin-left=2cm margin-right=1.5cm margin-top=1cm margin-bottom=2.5cm / fo:region-start extent=2cm/ fo:region-end extent=1.5cm/ fo:region-after extent=2.0cm/ /fo:simple-page-master fo:simple-page-master master-name=Following-Pages page-height=29.7cm page-width=21cm margin-left=2cm margin-right=1.5cm fo:region-body extent=24.7cm margin-top=3.5cm margin-bottom=2.5cm background-color=rgb(0,255,0) / fo:region-before extent=3.5cm/ fo:region-after extent=2.5cm/ /fo:simple-page-master fo:page-sequence-master master-name=rotex-offer fo:single-page-master-reference master-reference=First-Page/ fo:repeatable-page-master-reference master-reference=Following-Pages / /fo:page-sequence-master /fo:layout-master-set fo:page-sequence master-reference=rotex-offer fo:static-content flow-name=xsl-region-after fo:block space-before=1cm fo:table width=100% table-layout=fixed fo:table-column / fo:table-body fo:table-row fo:table-cell border-top=1px #00 solid fo:block text-align=right font-size=8pt padding-top=0.1cm fo:page-number/ / fo:page-number-citation ref-id=terminator/ /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:block /fo:static-content !-- Body -- fo:flow flow-name=xsl-region-body fo:block font-size=9pt xsl:apply-templates select=Offer_letter/ /fo:block fo:block id=terminator / /fo:flow /fo:page-sequence /fo:root Any ideas whats going wrong? best reagards Timo Jeremias Maerki Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RTF output
Tony Morris escribió: Thanks, by explicitly setting a width and height, the problem disappeared - it only occurred for the RTF renderer (though I only tried the PDF one as well). The sizes themselves seem to be a tad obscure though. Tony, can you be a bit more precise as to what you mean by this last sentence? All I know is that, in FOP Trunk, with 'height' and 'width' you only specify the dimension of the area. Use them in combination with 'content-height' and 'content-width' to get appropriate results. I don't have my test case with me, since I am at work at the moment. Otherwise, what I recall is setting the size of an external-graphic to the exact number of pixels (I think if I didn't, the RTF renderer wasn't happy), the image appeared scaled down, but if I set the image size to say, 10x the number of pixels, it would not appear 10x bigger than the scaled down image, but about the size I would expect normally. Granted, I was using MS Word 2003 for verification, which may well be the culprit. I will get more exact details when I go home. Tony Morris Software Engineer IBM Software Group, Tivoli Software Gold Coast, Australia (GMT +10) Sun Certified Programmer for the Java 2 Platform 1.4 Sun Certified Programmer for the Java 2 Platform 5.0 Sun Certified Developer for the Java 2 Platform I am an engineer. If I fail to accept what others accept, I earn their opprobrium. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
