This certainly explains why the browser rendered the code properly in ISO, when it should have rendered it properly in UTF-8. But the Response.CodePage = 65001 was the bit that was missing from the asp, which is why it wasn't sending the strings properly. All seems to be working fine now - thanks everyone :)
Karina > -----Original Message----- > From: Rákos Attila [mailto:[EMAIL PROTECTED] > Sent: 29 March 2007 14:42 > To: Karina Steffens > Subject: Re: [Flashcoders] ASP and Character encoding in flash > > > Flash doesn't care about the encoding given in XML's header, > it always treats the content as UTF-8 (even if it doesn't > match the real code page). Browsers however take the header > into consideration, so if > UTF-8 is given there, then they treat the content as UTF-8, and if > ISO-8859-1 is given, then as ISO-8859-1. So, if ISO-8859-1 > works well in browsers, it means that your text is in > ISO-8859-1, which is not suitable for Flash. > > The encoding of the text doesn't depend on the header, it is > just for informational purposes for parsers. If you change > the header, the text's encoding remains and doesn't change - > just parsers will interpret the same byte stream differently. > > So, you have to make sure to output UTF-8 encoded text with > your ASP application. > > Attila > > _______________________________________________ > [email protected] > To change your subscription options or search the archive: > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > Brought to you by Fig Leaf Software > Premier Authorized Adobe Consulting and Training > http://www.figleaf.com http://training.figleaf.com > _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
