RE: when to use language negotiation- author needed

Francois, 

Many thanks for volunteering !  Please be aware, however, that John
Yunker is working on some guidelines information for multilingual site
navigation, so please confer with him while developing your FAQ.

Btw, you or anyone else on a W3C member mailing list, can now write
directly to the public-i18n-geo list without me needing to forward.  If
you would like to be added to that list for receipt, let me know.

Cheers,
RI

============
Richard Ishida
W3C

contact info: http://www.w3.org/People/Ishida/ 

http://www.w3.org/International/ 
http://www.w3.org/International/geo/ 

W3C Internationalization FAQs
http://www.w3.org/International/questions.html
RSS feed: http://www.w3.org/International/questions.rss



> -----Original Message-----
> From: public-i18n-geo-request@w3.org 
> [mailto:public-i18n-geo-request@w3.org] On Behalf Of Richard Ishida
> Sent: 18 December 2003 09:17
> To: public-i18n-geo@w3.org
> Subject: Re: when to use language negotiation- author needed
> 
> 
> 
> Tex Texin a écrit  :
> > and decided we need an author for a faq on when it is 
> appropriate, or
> > not, to use language negotiation.
> 
> I'll take that.  Accomplices welcome.
> 
> -- 
> François
> > 
> > ========================
> > Some time was spent today discussing when this type of negotiation
> > should be used, and when alternatives should be considered. I was 
> > actioned with posing the question to the group, to collect 
> information
> 
> > and to solicit whether someone might be interested in 
> authoring a FAQ
> > or article on when to use this technique.
> > 
> > We thought Yves, John or François might have a special interest in
> > this subject and so I cc'd them individually.
> > 
> > For example, there were suggestions that this approach only 
> made sense
> 
> > where every page had an exact counterpart in another language or
> > region. Many sites have different pages or file 
> organization based on 
> > differences in content.
> > 
> > It might be the case that Language negotiation only makes sense for
> > the entry page and after that page is read and a language either 
> > defaulted or selected by the user, the rest of the content would be 
> > linked directly, without relying on language negotiation.
> > 
> > Some thought organization by language directory (e.g.
> > yadda/en/pages.html) might be more practical than by filename (e.g.
> > yadda/pages.en.html)
> > 
> > There were questions about server load and scalability.
> > 
> > There was also a discussion of roles and authorization, as content
> > developers may not have access to some server commands,  and we 
> > considered there is guidance needed for content developers and 
> > separate guidance needed for administrators.
> > 
> > So, we would like to ask if there is someone in the to-list 
> who would
> > like to author or contribute to a faq on the subject of when to use 
> > language negotiation and when not to, or defining 
> situations where are
> 
> > alternatives prefered.
> > 
> > Any takers?
> > 
> > 
> > 
> > 
> > 
> 
>

Received on Monday, 22 December 2003 06:17:38 UTC