possible ambiguity over fo:flow-map behavior

Glen Mazza <[email protected]>
Newsgroups gmane.org.w3c.xsl-editors
Message-ID <[email protected]>
Editors,

The fo:flow-map description appears ambiguous over
whether the source flow is to be duplicated (repeated)
into each target within the fo:flow-target-list, or is
to flow from one target to the next target
sequentially, in the order that the targets are
defined in the fo:flow-target-list.

Both have their use cases--in the case of duplication,
for example, to have the same text printed in opposing
side regions; or in the case of flowing from one
fo:region-body to the next, of having more power in
creating a newspaper-style layout.

>From http://www.w3.org/TR/xsl11/#fo_flow-map:

"For each fo:flow-assignment child of the fo:flow-map,
having an fo:flow-source-list child S and an
fo:flow-target-list child T, we say that the
fo:flow-map assigns -->each<-- of the flows referenced
by the fo:flow-name-specifier children of S to the
regions referenced by the fo:region-name-specifier
children of T."

"Each" here, to me, implies duplication/repetition
instead of flowing from one target to the next.  I'm
unsure if that was the SG's intent, however.

In the same section a similar ambiguity occurs.  While
the WD explicitly says *sources* are combined below,
the WD is somewhat vague on whether the *targets* are
combined or just have the source duplicated in the
multiple regions:

"The source list is a sequence of flow names whose
corresponding fo:flow objects (in the referring
fo:page-sequence) are treated as a single fo:flow for
composition purposes.  The target list is a sequence
of region-names which identify the region or regions
on each page which are used for the source content." 

I would recommend the text somehow be made clearer
indicating the layout intent for fo:flow-map.

Thanks,
Glen



		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.