CVS-based L10n packs for venkman (JavaScript Debugger)
Robert Kaiser
Last night I updated the venkman JavaScript Debugger to support
CVS-based language packs, see
https://bugzilla.mozilla.org/show_bug.cgi?id=394633
With that, the same process as for ChatZilla now applies to venkman and
can add localizations in l10n/<locale>/extensions/venkman/ which can be
used for getting a localized venkman through dependent language pack
add-ons. This can work in multiple ways:
1) Through SeaMonkey source L10n, the language pack for venkman is built
and included in localized SeaMonkey packages (in case the language built
for SeaMonkey also supports venkman L10n, else only the default venkman
with en-US will be included).
2) The pack can be installed in addition to the venkman package in all
applications supported by venkman. The pack can be either taken from a
SeaMonkey trunk build, with "make locales AB_CD=ab-CD" (use your code
instead of "ab-CD") from the objdir/extensions/venkman/ directory, given
your locale is supported and checked out next to the source tree, or
built with the makelocalexpi shell script with those commands (replace
"ab-CD" with your local code, note that only > marks are beginnings of
command lines, to make wrapping visible):
---------------------
> cvs -d :pserver:anon...@cvs-mirror.mozilla.org:/cvsroot co
mozilla/config mozilla/extensions/venkman
> cvs -d :pserver:anon...@cvs-mirror.mozilla.org:/l10n co
l10n/ab-CD/extensions/venkman
> cd mozilla/extensions/venkman/xpi/
> sh makelocalexpi.sh ab-CD
---------------------
For all variants, the locales/all-locales file in the venkman source
plays an important role: If your locale code is present there at its own
line, your locale will be built. If it is not present there, a langpack
will not be generated.
This enables venkman localizations to be optional.
So, as with ChatZilla, if you have checked in a complete venkman L10n,
please file a bug for getting included in the venkman all-locales file
and assign it to "kairo@", and I will add your locale there.
Moving DOM inspector or reporter to such an infrastructure is not
planned until this infrastructure is really well-tested, probably not
for the Gecko 1.9 (Firefox 3 / SeaMonkey 2) development cycle.
The dependent locale packs can be uploaded on AMO, I have filed a bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=412625 for making it
possible to install both an extension and a dependent language pack at
once, so it's as easy for a user as to install just one package. This
could also be achieved through comound XPIs. I hope we will get support
for this on AMO, so that extension localization and its usage will
become a really smooth experience.
Robert Kaiser