- From: Erik van der Poel <erik@netscape.com>
- Date: Tue, 02 Jun 1998 17:53:30 -0700
- To: Jason Pouflis <pouflis@eisa.net.au>
- CC: Aman Choudhary <aman@asu.edu>, www-international@w3.org
Jason Pouflis wrote: > > In developing Multilingual DNS, I came across the same problem. > It is solvable, and I am available for hire. > Multilingual Domain Names are also for sale. Is this a product? Or a service? How can I find out more about it? > >> < meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=" *"> > As far as I can tell IE4 forces the page to be displayed in the specified > charset, > if it is available. Any character data submitted by form is in that > character set as > binaries or NCRs (numerical character reference data of the form &#nnnn;). I believe NCRs are illegal in form submissions. Form submissions are plain text, not HTML. > However, I have not got an answer from Microsoft nor Netscape on this. Netscape submits the form in the same charset as the original HTML form. We don't use NCRs in form submissions. > (If anyone can give me the direct email for responsible people that would be > nice.) I am one of the responsible people at Netscape. > >It would be more reliable if > >you indicated the charset in the HTTP Content-Type header. (I'm assuming > >you're using HTTP.) > > >... > >echo 'Content-Type: text/html; charset=gb2312' > The charset tag is optional in HTTP 1.0, mandatory in HTTP 1.1. > Unfortunately, a lot of communication is stuck at HTTP 1.0, > meaning you will still need to put in the meta tag for content type. Are you saying that the HTTP charset is stripped by some proxies or other midstream agents? I.e. are you saying that even if you emit the HTTP charset from your server, it might not reach the client? Erik
Received on Tuesday, 2 June 1998 20:53:48 UTC