[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
On 14-02-07 11:20 AM, Graydon wrote:
I can see this working well within a page, in much the same way as the table works now in XHTML. If I do have to go with two columns in a single page, though, I'd go for the table approach because that allows me to have an additional left column with a paragraph number in it.
No, that's what is going to be problematic, for sure.
I don't know of any formatter extensions that do this, but I haven't looked very hard yet.
[xsl] Re: XSL:FO approach for facing-page translation
Subject: [xsl] Re: XSL:FO approach for facing-page translation From: Martin Holmes <mholmes@xxxxxxx> Date: Fri, 07 Feb 2014 12:55:49 -0800 |
On 14-02-07 11:20 AM, Graydon wrote:
On Fri, Feb 07, 2014 at 10:43:22AM -0800, Martin Holmes scripsit: [recto-verso text and translationHas anyone every done anything like this, and if so, do you have any advice? I can imagine that it might be done in a horribly manual fashion by trial and error, working page-by-page, but I really don't want to get into that. I'm happy to pre-process the text multiple times before it goes to the XSL:FO stage., Perhaps there are ways to measure (for instance) how much space a paragraph will take, and then adjust page-margins or spacing by small increments to preserve alignment between the two texts, but I haven't seen examples of such an approach.
The usual approach for keeping translations together is to use
<fo:list-item> <fo:list-item-label> <fo:block>ORIGINAL TEXT</fo:block> </fo:list-item-label> <fo:list-item-body> <fo:block>TRANSLATION</fo:block> </fo:list-item-body> </fo:list-item>
and set list-related parameters so you get the spacing you want, since lists allow full blocks at the label and item level while keeping things together at the top, so the units of text always start side by side.
I can see this working well within a page, in much the same way as the table works now in XHTML. If I do have to go with two columns in a single page, though, I'd go for the table approach because that allows me to have an additional left column with a paragraph number in it.
So far as I know, there isn't a mechanism to directly synchronize separate recto and verso flows; flow-maps can give you assignment of flows to regions, but that wouldn't give you synchronization between (across?) regions.
No, that's what is going to be problematic, for sure.
It's possible there's a formatter extension that does what you want? That's almost got to be easier than figuring out how to multi-pass adjust separate flows, since straight XSL-FO won't tell you how full the page is, you're not supposed to want to know that. :)
I don't know of any formatter extensions that do this, but I haven't looked very hard yet.
Cheers, Martin
-- Graydon
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] XSL:FO approach for facin, Graydon | Thread | Re: [xsl] XSL:FO approach for facin, Eliot Kimber |
Re: [xsl] XSL:FO approach for facin, Tony Graham | Date | [xsl] Re: XSL:FO approach for facin, Martin Holmes |
Month |
Keywords