cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stev...@outerthought.org
Subject [WIKI-UPDATE] LenyaI18N Sat Dec 27 16:00:06 2003
Date Sat, 27 Dec 2003 15:00:07 GMT
Page: http://wiki.cocoondev.org/Wiki.jsp?page=LenyaI18N , version: 102 on Sat Dec 27 14:25:03
2003 by RolfKulemann

- * __The initial document language served should be derived from a user agent's accept-language
header if available.__ Should mean, the accept-language overrides the default publication
language if the requested document is available in the accept-language.This would enhance
useability. Of course it costs some effort and the automatic part of negotiation does not
work in offline browsing mode. In case of offline browsing(pages are not served via a http
server) changing the language shouldn't be a problem since I assume a website provides links
to swtich the documents language. See the [Debian|http://www.debian.org/] website for a real
straightforward pattern of serving multilingual documents. Changing the browser's language
settings while watching the debian website causes every page to be displayed in the newly
set language as long as you do not specify a language identifier in the url. At the bottom
of the page, the user can access the language of the document being viewe!
d via hyperlinks. This pattern can also be used, if webpages are not served by Lenya but i.e.
by [Apache Http Server|http://httpd.apache.org/] using [mod_negotiation|http://httpd.apache.org/docs/content-negotiation.html].
Using this pattern fits imho best for the many cases where the user is able and aware of setting
his browser's accept-language. The pattern also suits well enough for the other cases, but
the user than has to switch the language on each page he visits, if the user agent doesn't
send the user's preferred accept-language. To implement this pattern as shown on the debian
website would mean to change the current behavior of Lenya, that if you request i.e. tutorial_de.html
all links in the returned page point to _de versions if available. The advantage of this behavior
is, that a user has to switch the language only once via a hyperlink, because the user is
directed to i.e. tutorial.de.html which contains links to other .de pages if available. Should
mean, the u!
ser is able to override his user agent's accept-language manually via hyperlinks. Imho, this
is a quite cool extension for the debian pattern of serving multilingual documents, but leads
into a maintenance problem, since all .de.html documents which reference documents without
language indentifier need to be changed, if a referenced document gets available in .de. I
propose to implement the debian pattern of serving multilingual documents as is.
?                                                                                        
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         !
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         !
                                                                                         
                                                                                         
                                                                                         
                  -

+ * __The initial document language served should be derived from a user agent's accept-language
header if available.__ Should mean, the accept-language overrides the default publication
language if the requested document is available in the accept-language.This would enhance
useability. Of course it costs some effort and the automatic part of negotiation does not
work in offline browsing mode. In case of offline browsing(pages are not served via a http
server) changing the language shouldn't be a problem since I assume a website provides links
to swtich the documents language. See the [Debian|http://www.debian.org/] website for a real
straightforward pattern of serving multilingual documents. Changing the browser's language
settings while watching the debian website causes every page to be displayed in the newly
set language as long as you do not specify a language identifier in the url. At the bottom
of the page, the user can access the language of the document being viewe!
d via hyperlinks. This pattern can also be used, if webpages are not served by Lenya but i.e.
by [Apache Http Server|http://httpd.apache.org/] using [mod_negotiation|http://httpd.apache.org/docs/content-negotiation.html].
Using this pattern fits imho best for the many cases where the user is able and aware of setting
his browser's accept-language. The pattern also suits well enough for the other cases, but
the user than has to switch the language on each page he visits, if the user agent doesn't
send the user's preferred accept-language. To implement this pattern as shown on the debian
website would mean to change the current behavior of Lenya, that if you request i.e. tutorial_de.html
all links in the returned page point to _de versions if available. The advantage of this behavior
is, that a user has to switch the language only once via a hyperlink, because the user is
directed to i.e. tutorial.de.html which contains links to other .de pages if available. Should
mean, the u!
ser is able to override his user agent's accept-language manually via hyperlinks. Imho, this
is a quite cool extension for the debian pattern of serving multilingual documents, but leads
into a maintenance problem, since all .de.html documents which reference documents without
language identifier need to be changed, if a referenced document gets available in .de. I
propose to implement the debian pattern of serving multilingual documents as is.



Mime
View raw message