Subject: RE: [xsl] XSL-FO: page-breaking with all block-containers having absolute-position="fixed" From: "Kyle Partridge" <kpartridge@xxxxxxxxxxxx> Date: Thu, 26 Feb 2004 16:57:55 -0500 |
Ken, >Have you tried empty blocks with a break: <block break-before="page"/> I did try, but it seemed not to work, with the absolute positioning. Maybe I missed something, though. I'll try it again. >But choosing "fixed" is basing your locations on the containing area. Have >you considered in your XSLT doing the arithmetic of positioning and >determining where a page break belongs? That would give you the option of >zeroing out your running top indicator at the last specified value for top >and reducing the subsequent values by that last specified value until you >run out of page size again. Yep. But that's what I was trying to avoid. If it's unavoidable I'll do it, though. :-) >Have you considered just using blocks and using a space-before= of the >difference between blocks? Using start-indent= and end-indent= will handle >your sides. I will give that a try too - but I suspect, due to the absolutely positioned nature of the document I'm trying to render, it won't look as much like the original document as people would like. Still, it remains to be seen... >I still don't understand why you are mapping an absolutely positioned set >of regions to a paginated medium ... I suspect you can get close to what >you want by just using blocks and letting the processor do the >pagination. Remember to use keep-together.within-column="1" to keep your >regions together on a single page (unless you don't mind the hard breaks in >the middle of a region). It's because we make a software program that has an arbitrary editing interface. You open it up, you click anywhere, and you enter text, or math. What you get is a page with "regions" arbitrarily placed. My job is to render that page, first as fo, and then as a PDF file. So the file must look just the way it looks in the software program. The program doesn't "flow" so my fo can't either...sadly. >Instead of the above, why not just use literal result elements and >attribute value templates: >None of the elaborate calculations you've given in your example need to be >done in <xsl:attribute> instructions. These are the kinds of things I often miss, due to my inexperience with XSLT. Thanks for the suggestions, I really appreciate them! >I hope this helps. You advice is always extremely helpful. Thanks, again! KP XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] XSL-FO: page-breaking wit, G. Ken Holman | Thread | [xsl] Trax and how to pass paramete, Paul Tremblay |
RE: RE: [xsl] Re: Network diagram -, cknell | Date | [xsl] Outputting A tag information, Vivek Shinde |
Month |