Hi Colin,
> >>>>> "david" == david n bertoni <[EMAIL PROTECTED]> writes:
>
> david> It's a proprietary extension, although any C++ DOM can
> david> almost be considered proprietary, I guess. You can still
> david> do this with the DOM Xalan-C generates, right?
>
> The xerces DOM, yes.
>
> It's just a maintenance thing - both the transform (if I want direct
> output), and the DOM code have to be kept in line. Still, it's mostly
> just the XHTML 1.1 DTD, so it's no big deal.
>
> But couldn't xalan do the same thing automatically?
Yes and no. When you explicitly provide a FormatterListener instance in
the XSLTResultTarget, we ignore most of the xsl:output information. If we
didn't, then there would be no way for users to overide xsl:output, and
we'ed get complaints about that. Also, it would require that Xalan-C
understand what sort of FormatterListener instance it's working with, which
it cannot do. For example, the encoding attribute of xsl:output is not
relevant for a DOM FormatterListener, while it is for those that are
serializers.
Dave
