XUL is so flexible that creating localized extensions is incredible easy, adding new languages is simple and the developer effort is very low.
So adding locales is technically trivial but having locales updated can have a dramatic impact on release process.
Everything is based on voluntary contribution and this is simply awesome but very often localizers stop translation without tell anything, other translators can’t respect deadlines, this is voluntary activity so if they can’t do it means simply they can’t do!
I’m very sad but I’ve decided to drop localizations inclusion from my extensions I leave only my mother tongue and obviously English.
A short list of attempts I’ve done to obtain completed locales but without success
- Contacting localizers asking to complete localization without receiving reply (bad citizens???)
- Searching other people to continue translations
- Asking translations for less than ten strings per release (including accesskeys and key)
- Setting long deadlines (two/three weeks) discarding periods closer to holidays (summer/winter)
I know there are many ways to have an incomplete locale using en-US for missing strings, (read Firebug lesson) but I really dislike mixed locales and I’m a zero-or-one man so complete locales go inside XPI, incomplete locales not bundled!
So finally I’ve decided to stop locales inclusion, I will continue to write code compliant with locale rules (eg no hard coded strings) because it’s easy and really useful.