Re: Source L10n for extensions (ChatZilla, venkman and others)
Axel Hecht <[email protected]> Thu, 27 Sep 2007 13:14:48 +0200
| Newsgroups | gmane.comp.mozilla.devel.jsdebugger |
|---|---|
| Message-ID | <nIudnbGlifsKDWbbnZ2dnUVZ_uOmnZ2d__42899.6978480884$1190891730$gmane$org@mozilla.org> |
Robert Kaiser wrote: > Gijs Kruitbosch wrote: >> What the SeaMonkey L10N people do is up to them. We stop touching >> ChatZilla on SeaMonkey immediately after the first release, unless >> there are security issues that need to be addressed. We would probably >> deal with l10n freezes on seamonkey's side easily as we don't really >> check in stuff every day or whatever... > > Yes, we're happy to manage that from the SeaMonkey side, as long as we > are allowed to mess with the all-locales file to adjust it to satisfy > localizers' requests :) > > Robert Kaiser > This is a recipe for disaster. If the chatzilla folks don't want a localization process, we shouldn't do one. I don't see a compelling story here to request AMO resources for this, too. I could, but there had to be a better plan. Regarding the "it should just work", that's untested. In particular things like installing the dependent language pack together with the chatzilla add-on, i.e., the blocking add-on isn't active yet. Doing multi-item install triggers, too. The various update paths are untested, too, I think. Really, we shouldn't invest a lot (and I won't) until we have all this actually tested, as I'm not sure if we'd get bugs fixed, if we find some. In particular not if there's no backup from the extension community to actually fix something. Axel