[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
RE: [xsl] character encoding with MSXML3
Subject: RE: [xsl] character encoding with MSXML3 From: "Joshua Allen" <joshuaa@xxxxxxxxxxxxx> Date: Fri, 22 Jun 2001 21:01:20 -0700 |
Hmm, this one is an area it looks like the spec was loose: http://www.w3.org/TR/xslt.html#section-HTML-Output-Method says: "The html output method may output a character using a character entity reference, if one is defined for it in the version of HTML that the output method is using." It says "may" instead of "should" or "must", according to: http://www.ietf.org/rfc/rfc2119.txt, that means it is "truly optional". Of course, that legalistic explanation doesn't help much in solving your problem, though. What's the scenario that makes the actual character unacceptable and requires use of the entity from HTML DTD? Technically, to a browser, the é should be treated as if it is the alt-130 character anyway, right? I'm not questioning the fact that you need this, just wondering what the specifics are since I haven't run into this before. -J > -----Original Message----- > From: MacEwan, James (Information Services) > [mailto:James.MacEwan@xxxxxxxxxxxxxxxxxx] > Sent: Friday, June 22, 2001 7:35 AM > To: 'xsl-list@xxxxxxxxxxxxxxxxxxxxxx' > Subject: [xsl] character encoding with MSXML3 > > Hi xsl-list'ers, > > I am creating HTML documents that are bilingual (English and French) (i.e. > using <xsl:output method="html">). > I successfully have Saxon putting out those special HTML Latin characters > (e.g. é) for my French output. > > I do not have such success with Microsoft. It puts out the actual small e > acute -- what you get when you type ALT-130 on a Windows box in notepad. > Unfortunately for now, I am stuck with Microsoft's MSXML parser. > > Does anyone know if there is a setting in Microsoft's parser to get it to > put out "é"? Or perhaps I am missing something in my xsl:stylesheet > declaration? > > (BTW: The XSLT Test tool is a great way to quickly compare output between > different XSL implementations. > http://www.netcrucible.com/xslt/xslt-tool.htm > ) > > Thanks. > > My XML (note the encoding is ISO not UTF) --------------- > <?xml version="1.0" encoding="ISO-8859-1"?> > <dtdTest> > <ENGLISH_MENU>Client Statements</ENGLISH_MENU> > <FRENCH_MENU>Relevés clients</FRENCH_MENU> > </dtdTest> > > My XSL --------------- > <?xml version="1.0" encoding="UTF-8"?> > <xsl:stylesheet version="1.0" > xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> > > <xsl:output method="html"/> > > <xsl:template match="/"> > <html> > <xsl:apply-templates select="dtdTest"/> > </html> > </xsl:template> > > <xsl:template match="dtdTest"> > <body> > <xsl:apply-templates/> > </body> > </xsl:template> > > <xsl:template match="ENGLISH_MENU"> > <xsl:value-of select="."/> > </xsl:template> > > <xsl:template match="FRENCH_MENU"> > <xsl:value-of select="."/> > </xsl:template> > > </xsl:stylesheet> > > My happy output using Saxon --------- > <html> > <body> > Client Statements > Relevés clients > > </body> > </html> > > My less happy Microsoft output (apologies to all whose systems have munged > the e-acute below) -------- > <html> > <body> > Client Statements > Relevés clients > </body> > </html> > > > > James MacEwan > Software Developer > Investors Group Inc. > mailto:James.MacEwan@xxxxxxxxxxxxxxxxxx > v: (204) 956-8515 > f: (204) 943-3540 > > "I don't know, lad. It's like no cheese I've ever tasted." -- Wallace > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] character encoding with MSXML, MacEwan, James (Info | Thread | RE: [xsl] character encoding with M, MacEwan, James (Info |
RE: [xsl] Installing MSXML3 in repl, Joshua Allen | Date | [xsl] Re: xsl:transform, Dimitre Novatchev |
Month |