This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: encoding issues


> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of Andrew Welch
> Sent: Wednesday, July 03, 2002 12:03 PM
> To: xsl-list@lists.mulberrytech.com
> Subject: RE: [xsl] encoding issues
>
>
>
>
> >I think what's going on is that you're expecting to "see" the result of
> >putting a space or sequence of spaces into the xml file when you view
> >the xml file in IE(or is it that you want the whitespace to be
> >maintained on output itself?). That won't happen since xml files are
> >supposed to ignore whitespace, now if you put xml:space="preserve" as
> an
> >attribute on the element you want the whitespace to be significant in
> my
> >understanding is that it should be displayed.
> >However my experience with IE is that it does not display it, perhaps
> >this is a bug in the Defaultss.xsl.
>
>
> preserving whitespace only preserves whitespace only text nodes, which
> is a different matter.  What I am wondering is:
>
> 1. How IE decides which encoding to use
> 2. Why MSXML4 doesnt output unicode if you specify encoding="utf-8" in
> xsl:output

Probably unrelated, but still...: if your running transforms in IE (using
the stylesheet PI), you *never* use MSXML4.

Julian


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]