This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: default encoding with no xsl:output element specified?
- From: Kendall Shaw <queshaw at pacbell dot net>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Wed, 27 Mar 2002 19:43:37 -0800
- Subject: Re: [xsl] default encoding with no xsl:output element specified?
- References: <000e01c1c357$c5e22db0$66816bd5@pcukmka>
- Reply-to: xsl-list at lists dot mulberrytech dot com
Michael Kay <michael.h.kay@ntlworld.com> writes:
> > I only see mention of what the default is if you omit the encoding
> > attribute from the xsl:output element. What if there is no xsl:output
> > element?
> >
> The spec says that the effective value of the encoding attribute is the
> result of merging all the <xsl:output> elements in a particular way. This
> rule has the effect that if there is no encoding attribute in any
> <xsl:output> element, the behaviour is the same as if there is no
> <xsl:output> element.
I keep having a nagging question about this, because I keep reading
people saying UTF-8 is the default. Isn't it implementation defined:
UTF-8 or UTF-16 that is the default?
Kendall
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list