Lists Home |
Date Index |
- From: "Frank Boumphrey" <firstname.lastname@example.org>
- To: "Andy Dent" <email@example.com>, <firstname.lastname@example.org>
- Date: Fri, 11 Sep 1998 23:08:31 -0400
>I've seen slightly conflicting suggestions. In some postings it's been
>suggested that there is not currently a standard way to HIDE content.
my understanding was that if you didn't want to display an object you just
ommited to process the children.
would result in a styled text flow object, "Hello XSL!"
>Is there some exclusion rule on formatting objects that says, once an
>element has been consumed by one object, it is effectively obscured from
Again it was my understanding that the XSL processor looked for the best
match for any source element, and just made one template for each source
Once it had found it it went on to the next.
you can however use the <xsl:process select....> to create different views
of the same source element.
What is not clear to me at the moment is how one orders the result tree in
an order that is different from the source tree.
>1) headers contain some flow objects (page number, count, current date) as
>well as data. Some of that data may not appear anywhere else in the report.
>Thus, the items in a header are a mixture of data content (should appear in
>the plain XML) and flow objects (appear in the XSL). It has taken me a
>while to resolve exactly WHERE in the XML the data content should appear.
Actually the processor should use the source XML document + the XSL style
sheet to construct a brand new tree. What is rendered as flow objects are
the nodes of the brand new tree, and it doesnt matter whether these nodes
were derived from the source document, the style sheet, or were infact
generated as page numbers would be.
From: Andy Dent <email@example.com>
Date: Friday, September 11, 1998 9:28 PM
Subject: page header footer resolution
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)