I'm working in the l10n project and I didn't find anywhere how is going to be handled the modularity and the language. Most of the translators will release an installable langpack.xpi or a complete localized build for the Mozilla 1.0 release. If there is an update in one of the modules (i.e.: pipnss) adding something new, including a couple of UI strings. How will those strings be localized without installing a new langpack.xpi with the correct version? In my experience, if you are lucky you will find the new strings unstranslated, although more probably you won't find them, and to be more reallistic, you won't find any of the pipnss strings and non of its features will work.
I didn't find any document stating how those things will be done, and I would like to hear what other people says about this. My proposition is: - When there is a module that is going to be updated, before is released to everybody send an email to the l10n mailing list, so everybody is informed. - The l10n teams can generate a small .xpi or .jar than can be shipped with the module. - I don't know how the modularization will work, but I suppose will be something as installing a new langpack.xpi. The best way could be to detect which language(s) your Mozilla is using, and then download and install the module plus the .jar files for each of the languages. - If a language is not available, and to prevent crashes, the best thing would be to install the English .jar, so all the module strings will be displayed in English (or to recommend the people using that locale to wait a few more days and see if your locale is available). I have mailed this to the l10n newsgroup, but I thing the discussion should go on in seamonkey. Xose S Puente l10n contributor
