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

Re: Non Latin1 charsets (draft-holtman-http-negotiation-00.txt)

From: Mirsad Todorovac <tm@rasips2.rasip.etf.hr>
Date: Fri, 1 Mar 1996 11:45:48 +0100 (MET)
Message-Id: <199603011045.LAA29304@rasips2.rasip.etf.hr>
To: Nickolay Saukh <nms@nns.ru>
Cc: koen@win.tue.nl, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
> 
> 4.2 Accept-Charset
> 
> I think last sentence of first paragraph should be written as
> "The ISO-8859-1 character set can be assumed to be acceptable
> to all user agents.". Rationale: per HTTP/1.1 draft
> (section 3.7.1) entity body without explicit charset can be
> US-ASCII only or ISO-8859-1. Thus any conforming user agent must
> be able to handle ISO-8859-1.
> 
> 4.6 Alternates
> 
> Can media-type contain charset? Is this a valid exmaple?
> 
> Alternates: {"TheProject.fr.html" 1.0
>       {type "text/html"} {language "fr"}},
>     {"TheProject.en.html" 1.0
>       {type "text/html"} {language "en"}},
>     {"TheProject.ru.html" 1.0
>       {type "text/html;charset=iso-8859-5"} {language "ru"}}
>     ("/cgi-bin/xlate?koi8-r+TheProject.ru.html" 1.0
>       {type "text/html;charset=koi8-r"} language "ru"}}
> 
> 5.1 Reactive negotiation
> 
> If two alternates are differ by charset only, how
> specify preferred one?

By the quality factor.  This has been promoted in Lynx browser, and
I havent been able to see Netscape and Mosiac NCSA support this. -- Mirsad

-- 
    | Mirsad Todorovac					|
    | Faculty of Electrical Engineering and Computing	|
    | University of Zagreb				|
    | Unska 3, Zagreb, Croatia 10000			|
    |							|
    | e-mail: mirsad.todorovac@fer.hr			|
Received on Friday, 1 March 1996 03:02:29 EST

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