On 2008-03-11, Dragon wrote: > 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? Then the user would click the link to get a cookie that would override the transparent content negotiation process. The idea of content negotiation is to suggest the best possible version automatically. > 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. -- Daniel --------------------------------------------------------------------- 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: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|