Subject: RE: [xsl] Problem with rendering of   From: "Passin, Tom" <tpassin@xxxxxxxxxxxx> Date: Wed, 14 Apr 2004 16:23:26 -0400 |
> From: Richard.McMillian@xxxxxxxx [mailto:Richard.McMillian@xxxxxxxx] > This thread addressed the problem back in 2002. Has anyone > come across a better solution? > > http://www.biglist.com/lists/xsl-list/archives/200211/msg00172.html > Sure, Julian Reschke posted it earlier today. The MS component always generates utf-16 when you use it to create strings instead of objects. Thus there ends up being a mismatch between the declared encoding and the actual encoding. This is pretty much a FAQ by now, but until you posted your code no one could tell what you were invoking the problem. The solution is not to futz around with the meta element and trying to trick the browser, but the generate the output using objects instead of strings. Once the encoding discrepancy is fixed, the presence of the meta element will not cause any problems and could even be beneficial (as when the document is loaded from a file, and thus has no headers to state the encoding). Cheers, Tom P
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Problem with rendering of, Richard . McMillian | Thread | Re: [xsl] Problem with rendering of, Mike Trotman |
RE: [xsl] Problem with rendering of, Richard . McMillian | Date | [xsl] CDATA question, Uslu, Cihan Y (MED) |
Month |