Page: http://wiki.cocoondev.org/Wiki.jsp?page=LenyaI18N , version: 91 on Sat Dec 27 11:57:16 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 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. But this is a topic of offline page generation, where the topic ''serving multilingual documents in offline mode'' should be covered. 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 viewed 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. ? ^^^ ^^^ + * __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 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. But this is a topic of offline page generation, where the question of ''how to serve multilingual documents in offline mode'' should be covered. 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 viewed 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. ? ++++ + ^^^^ +++++++ ^
