Note that you need to create a SUMO account and log in to see the
listing, because they are still in the "staging" category, which means
they are not seen by regular visitors of the site.
So far, translators/localizers for 17 locales have been contacted, and 6
of them have responded.
However, there are 19 locales which I've been unable to find contact
information for. Does anyone know more about these translations? I tried
to look in the CVS history, but that didn't seem to work on these files
for some reason (error messages like "Rcs file, accessibility.xhtml,
does not exist").
For the details, see this list of locales and their status:
http://wiki.mozilla.org/Support/In-product
Did you use http://wiki.mozilla.org/Category:L10n_Teams ?
That and you can use bonsai, too, you have to fix the links from lxr by
hand, though. For example,
http://bonsai-l10n.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=MOZILLA_1_8_BRANCH&branchtype=match&dir=&file=l10n%2Fde%2Fbrowser%2Fchrome%2Fhelp%2F&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=all&mindate=&maxdate=&cvsroot=%2Fl10n
tells you a bit. It does give some contributor names and bug references
which have more contributors, too. Just for reference for the ugly other
thread.
Axel
Thanks for your helpful points. With the help of a list from Pascal, I
have been able to contact 35 of the 36 locales (the only one remaining
is "rw")!
So far, 18 localizers have responded that they are going to have a look
at the imported content and later on update it for Firefox 3!
I forgot to look there after processing Pascal's near-complete list.
Thanks for reminding me. :)
So we need can translate the Articles in SUMO now?
So we can translate the articles in SUMO now?
Not yet. There are still some patches that need to be applied and tested
to make translating easier.
<http://blog.mozilla.com/sumo/roadmap/> (See milestone 0.5)
There's a link to the bug list; and you can help test the patches at
support-stage.mozilla.org.
See the "SUMO localization checkins" post I published today. We're
getting closer to full l10n support. :)