W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 1999

Re: Content negotiation example needed.

From: Masafumi NAKANE <max@wide.ad.jp>
Date: Sat, 11 Sep 1999 11:59:37 +0000
Message-ID: <14298.17449.143116.71148G@fr.aslm.rim.or.jp>
To: cpl@starlingweb.com
Cc: w3c-wai-gl@w3.org
I'm nottoo sure if this is a kind of information you need, or I don't
know too much about it, but ...

First, I don't know any markup or scripting to enable content
negotiation.  At least I couldn't find any markup for this purpose
within HTML 4.0 specification.  I guess maybe there is some scripting
technique, but I'm not familiar with kinds of scripting used on the
Web at all.

Typically, document provider prepares several files for the documenht,
one file for each language and/or character encoding, etc. to put on a
server that has capability for content negotiation.  (Most popular
servers have this function nowadays, I think.)  If the document in
question has English version and Japanese version, they would be named
as foobar.html.en and foobar.html.ja.

On the client-side, user would set the preferred language.  Lynx has
an item for this in its options menu.  If you set this preference to
``ja'', for examples, and access foobar.html, the server returns
foobar.html.ja.  If you don't set this option, the server returns the
document in the default language, which is configured by server

You can find a real-world example at:
with ``ja'' set to the language preference in your browser, you get
the Japanese version.


At Fri, 10 Sep 1999 22:04:58 -0400,
Chuck Letourneau <cpl@starlingweb.com> wrote:
> For Checkpoint 11.3, "Provide information so that users may receive documents
> according to their preferences"
> The Techniques Document has the following example:
> "1) Instead of including links such as "Here is the French version of this
> document", use content negotiation so that the French version is served to
> clients requesting French versions of documents."
> I have never seen markup (or scripting) that actually shows how to do content
> negotiation.  I honestly don't even know if it is only something that can be
> done server-side or if it can be done client-side. 
> I need to include a meaningful example in the EO WCAG Curriculum that will show
> students how to actually do it (or what it means to be able to do it), and  be
> able to explain the concept in a few words.  
> I also can't think of any reason that the same example couldn't be included in
> the WCAG Techniques document, since the current example isn't really an example
> at all.
> Thanks in advance,
> Chuck Letourneau
> ----
> Starling Access Services
>  "Access A World Of Possibility"
>   e-mail: info@starlingweb.com
>    URL: http://www.starlingweb.com
>     Phone: 613-820-2272  FAX: 613-820-6983
Received on Friday, 10 September 1999 23:04:22 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:07:16 UTC