Daniel Aleksandersen wrote:
Hi,
I need some help to think clearer.
To copy the example used on âMaking readable URIsâ at W3C:
âA Norwegian without knowledge of basic English would like to be able to
remember "www.site.com/fiske/stenger" instead
of "www.site.com/fishing/rods".â
What I am wondering about is how I would go about rewriting the URIs in
Apache to allow for content negotiation at these two URIs. If a Norwegian
requests âwww.site.com/fishing/rodsâ, he should get redirected to the
Norwegian URI and served the Norwegian document. Say the location of the
two versions is "/fishingrods.html.en and fishingrods.html.nb.
---------------- End original message. ---------------------
But what if a person with a non-English language
preference actually wants to view the English version?
I don't know if forcing the language to match the
user's language preference regardless of the URL
requested is necessarily a good idea. One example
I can think of off-hand would be if somebody were
learning a language and wanted to see both
versions for comparison. Or maybe if the
maintainer of both versions had Norwegian set and
wanted to look at the English version without
having to change language preferences.
Dragon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
