W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1996

Re: Round 3: moving HTTP 1.0 to informational

From: Nickolay Saukh <nms@nns.ru>
Date: Mon, 12 Feb 1996 20:32:43 +0300
To: yergeau@alis.ca
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <28050.824146363@Alyona.office.nns.ru>
> And most clients default to whatever is 
> the character encoding of the platform they're running on.  If you 
> run Mosaic on Russian Windows, it defaults to Microsoft's version of 
> a cyrillic code page, without even the possibility of displaying 
> ISO-8859-1.  This is current practice.

Not true. It just displays text with configured fonts. I can display
iso-8859-1 after manual reconfiguration of fonts. There are browsers
which can switch fonts automagically (Alis among them). But most of
browsers (Macintosh ones are exception) did not translate incoming
documents/outgoing form data from "native" encoding to network one.
Even does not provide charset information for server. That is why
enforced to use User-Agent by servers in attempt to guess browser
native encoding.
Received on Monday, 12 February 1996 09:36:52 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:31:45 EDT