Subject: Re: [xsl] Page-break/Static content From: Paul Grosso <pgrosso@xxxxxxxxxxxxx> Date: Thu, 28 Dec 2000 16:53:36 -0600 |
At 17:36 2000 12 28 -0400, Arved Sandstrom wrote: >Two, Tobi tripped up on a FOP feature (that I must take the blame for) that I >hope people don't actually use until things in the spec have been resolved some >more. Namely, it is my position that the XSL spec is ambiguous as to whether a >page-sequence can only contain one flow, or more. > >Here is an excerpt from section 6.4.5 of the spec: > ><excerpt> >The default ordering constraint of section 4.7.1 (General Ordering Constraints) >does not apply to the fo:page-sequence. The default ordering constraints apply >to the child fo:flow objects; special ordering constraints apply to the child >fo:static-content objects. > >Contents: (title?,static-content*,flow) ></excerpt> > >The BNF grammar says one fo:flow; the paragraph before the BNF says multiple. >Which one is the typo? Who knows? There is no language anywhere else in the >spec that treats the multiplicity of fo:flow within a page-sequence. > >Normally I would treat the BNF like the gospel itself - in this case I don't. >In particular I can think of situations (practical ones, not just pathological >examples) where the ability to have 2 flows in a page sequence would be pretty >handy. > >In any case, the effect of this is - IF you want to experiment, you can >currently use multiple fo:flows in FOP, within one page-sequence. I would not >do production stuff with any more than one fo:flow per page sequence, since >none of the other XSL-FO implementations support this viewpoint. I had noticed this earlier and checked with others on the XSL FO subgroup. The idea, as Steve Zilles and I agreed, was that for XSL 1.0 there should be exactly one flow per page-sequence. We realize that the ability to allow multiple flows is useful, and we have planned ahead to allow it in XSL 2.0, but it is not there now. (The text was written so as to work even once multiple flows are allowed, but the BNF should be taken--at least in this case--as definitive for XSL 1.0.) In the future, it should be possible to flow into, say, both the region-body and the region-start, but that capability is not in XSL 1.0, and for XSL 1.0, it is an error for there to be more than one flow in a page-sequence. paul XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Page-break/Static content, Arved Sandstrom | Thread | Re: [xsl] Page-break/Static content, Arved Sandstrom |
RE: [xsl] Dynamic creation of frame, Chris Bayes | Date | RE: [xsl] Carrying Namespaces throu, Julian F. Reschke |
Month |