Hi everyone :)Since I was last involved in discussing this topic, I have been away. I'd like to catch up with the status of content negotiation for the OOo website and wiki.
I can see that the OOo website generally has been improved. And I've read the posts about new functions for the wiki. This is all good stuff. :)
Do either of these improvements include content-negotiation?In particular, we want the webpage to respond to the browser's language preference. That means the user gets a page s/he can read, not a jumble of meaningless symbols. (To experience this, try going to a page written in an alphabet you can't read.)
This is important, for example, because the OpenOffice.org Help, regardless of translation, points users to the English mailing lists, Wiki, FAQ and forum. You can't localize that information: gsicheck won't allow it.
How far have we got towards effective content negotiation? Thankyou in advance for bringing me up-to-date. :) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n
PGP.sig
Description: This is a digitally signed message part
