The language to use for internationalization can be chosen in various ways
- via http parameter 'lang', e.q http://exist/index.html?lang=de - as xquery parameter $selectedLang if the i18n module is called
- xml:lang attribute on the root node of the markup to process
Why doesn't the i18n module also have a fourth (or possibly
two-and-a-halfth) alternative of finding the language from the HTTP
'Accept-Language' header, e.g.:
I could, of course, modify my app to start passing around a 'lang'
parameter, but I'm wondering why I should have to instead of having the
option of defaulting to using the browser's opinion of the language to use.
Antenna House, Inc.