Community feedback on Localization and translation woes provides incentive to change. Arabic localization was provided in a format that we could not easily integrate into the core. A professional translator gave feedback during the Madagascar
Tools mentioned by Mozilla:https://pontoon-dev.mozillalabs.com/?url=&locale=de
(what they're moving to)http://translate.sourceforge.net/wiki/pootle/index?redirect=1 (current)
Current Process has translators going to Github and Transflex or, for mobile, Google docs. This is not effective for our community. It is a barrier to entry.
Transiflex research
There is a bug with nested arrays which Henry has been investigating.
Technical Issues
1. Can we temporarily reinstate tafsiri until we have viable solution - Henry to investigate with Brian
2. Test Tafsiri - heather to request michelle and sophie to test tafsiri and Transiflex
Update on April 26, 2012 - Brian H. advised that Tafsiri cannot be reinstated. We won't test it.
3. Robbie to test https://pontoon-dev.mozillalabs.com/?url=&locale=de
Update on April 26, 2012 - Robbie and Henry continue to test.
4. what are the software requirements for a translator - heather and michelle
5. what are the tech team restrictions - robbie
6. what community /board goals - juls we need to get to 25 translations by the end of the year
7. Heather to write a blog post about localization, our fail and the next steps.
Update April 26, 2012 Blog post on hold pending testing.