Re: Source L10n for extensions (ChatZilla, venkman and others)

Rimas Kudelis <[email protected]> Tue, 11 Sep 2007 07:47:47 +0300
Newsgroups gmane.comp.mozilla.devel.jsdebugger
Message-ID <[email protected]>
Gijs Kruitbosch rašė:
> The trade-off for adding all these localization is not trivial - for
> ChatZilla's jar file, the en-US locale is about 10-15% of the total
> jarfile. Which means if you add 10 or so locales, half the jar (and
> hence xpi) is localizations (90% of which the user will not need).
> That's not really reasonable.

First, I was talking about standalone extension here. With SeaMonkey
it's easier, as you know a priori which locale the user wants to use for
Cz when he downloads SM. So, for the SM case, I think it's absolutely OK
to only include one locale.

> Only installing some of them from one single download is not possible at
> this time, to my knowledge. While you can put multiple add-ons in one
> xpi, I don't think that the current add-ons UI lets you pick which of
> those you want to install, so doing that would not solve our problem. It
> is probably too late in the game for the 1.9 cycle to add UI for that.

Is it?

> And besides, in those cases we would still need the separate
> l10n-specific xpi files which were proposed in my earlier post (so your
> idea could be a later addition to this).

Yes. What I'm concerned about is not the way extensions are packaged,
but rather the way they are distributed. I believe that the less
seeking/reading the user has to do to download what he wants, the better.

> As far as AMO is concerned - if we could find a solution for that stuff,
> that'd be great. I'm not sure how easy it would be - you would have to
> ask the AMO folks.

One thing that I'm not sure about is how AMO would find out which locale
I actually want. Will it ask me, or will it make some decisions based on
my IP or my UA language, or what?

RQ
_______________________________________________
dev-apps-js-debugger mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-apps-js-debugger