Amir Rosen wrote:



-----Original Message-----
From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 11, 2003 8:22 PM
To: [EMAIL PROTECTED]
Subject: Re: Encoding problems


Vadim Gritsenko wrote:


Stefano Mazzocchi wrote:
...



On the other hand, by placing

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>


the server creates an HTTP header that instructs the user-agent about

the encoding. This solved the encoding problem on *all* browsers.



Why not simply patch the serializer to set proper


content-type header?



Because it will not work for cached content ?



Then cache has to be fixed, that's it.
Adding <meta/> to the XSLT is soooooo hacky! What if you have your output encoding determined dynamically?


Vadim




Reply via email to