Forum OpenACS Q&A: How to deal with non english speaking users
I was wondering though if it wouldn't make sense to have a whole "Spanish" subsite, with it's own bug-tracker, file-storage and forums.
my only worry would be forums essentially being 'forks' and information not flowing back and forth, but thats not happening anyway, so i say yes to both ideas.
This way we can avoid having two different communities that people that understand both languages would have to track.
Once a forum message or bug is submitted in Spanish, someone can do a quick translation to English or just resolve it.
I like the idea of using the existing forums. Users post in whatever language they feel best conveys their message. Replies might be in a different language, too. Maybe search could be modified to filter by locale?
I find myself regularly googling to pages where the solution is in a language foreign to me. Often the information is useful, because the code (consisting of reserved words) tend to be consistent. If I need to translate, I ask for help.
That stated, I am sure that a locale-oriented openacs website would be welcome, and may be a way "demo" il8n features.
For example, are you expecting developers to understand/translate bugs logged in all languages?
I think that promoting more than one language at openacs.org is a mistake and will lead to isolated conversations and more noise (as questions may need to be reposted in a different language to reach members who can answer it).
My 2 cents.
The problem here is that lots of people in the world don't know English, so either we ignore them or we allow them to post in any language in the hope that their info would be useful.
> For example, are you expecting developers to understand/translate bugs logged in all languages?
Of course no, but it's better to have a bug report in a non English language than no bug report at all.
> I think that promoting more than one language at openacs.org is a mistake and will lead to isolated conversations and more noise (as questions may need to be reposted in a different language to reach members who can answer it).
I already proposed to keep conversations English whenever possible.
A quick and dirty option...
In my travel trade network I face a similar problem. I have created a weblog that shows a category called "BreakingNews" and lists all countries in the world. eTurboNews has local correspondents in 150 countries. The idea is to contact the local reps and explain them they can communicate with their local audience in their own language.
The only prerequisite is that users change the default language setting. This will create a multi lingual news site, where the navigation is localized using OACS internationalization.
Behind the scenes the local reps, who speak English, take care of creating an condensed English language edition, so important issues are dealt with.
The full blog will look rather stupid with all those languages, but if users subscribe to their own (country category)language prefference it all starts to make sense.
It might be an idea to highlight the "change language" feature on oacs.org because the functionality is hidden, conterary to the default oacs install.