• From: "Ollikainen, Jari" <Jari.Ollikainen@q...>
• To: 'Michael Brennan' <Michael_Brennan@A...>
• Date: Fri, 29 Jun 2001 17:12:34 +0300

> -----Original Message-----
> From: Michael Brennan [mailto:Michael_Brennan@A...]
> Sent: 26. kesäkuuta 2001 23:43
> To: Ollikainen, Jari
> Cc: 'Bob DuCharme'; xml-dev
> Subject: RE: UTF-16 -> UTF-8
> 
> 
> You have to watch out for the interactions with ASP, though. 
> ASP has it's
> own way of dealing with character encodings that is 
> completely independent
> of the XML technologies.
> 
> The key thing to watch out for is the Response.Write method. It always
> abides by the "codepage" in effect, which is typically some 
> variant of one
> of the ISO-8859 set of encodings. To change this, you can 
> explicitly set the
> codepage and Content-Type header to do the right thing:
> 
> <%
> 	Session.Codepage=65001
> 	Response.ContentType = "text/xml; charset=UTF-8"
> 	...
> %>
Yup. This works... sort of... anyway I got the idea how to do it! Thnks!

--
Q u a r t a l   O y

Jari Ollikainen, Software Developer (jari.ollikainen@q...)
mobile +358 [0]424 258 246
fax    +358 [0]424 258 360

http://www.quartal.com

• Prev by Date: DSSSL dates (was Re: SGML vs XML)
• Next by Date: XML and server-side inclue or external javascript files
• Previous by thread: RE: UTF-16 -> UTF-8
• Next by thread: RSS and MyNetscape problems
• Index(es):
  • Date
  • Thread