L10n and SeaMonkey 2 Alpha 1
Robert Kaiser
As you might know from my previous posts, SeaMonkey 2 Alpha 1 will not
be released with localized builds. The night after we had cut the a1
source, I decided though that we could try and have a few langpacks of
what happens to succeed building right now, just for testing. So I
downloaded the lackpacks created for the first 2.0a2pre nightly, and now
hacked up a script that injects the en-US versions of the
downloadmanager and wallet files into them (which are missing from
source L10n), which should make an otherwise complete langpack actually
work.
I processed de, es-ES, fr, lt, pt-BR, ru and sk that way, as those were
green for the first 2.0a2pre nightly, and roughly tested the langpacks
by installing them, activating them and opening browser, add-ons manager
and preferences (where we had the last changes) with all of them, and it
turned out that only de, fr and lt had the last change, all others broke
in preferences.
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0a1-candidates/build1/langpack/
has those three langpacks and we'll have those as "experimental language
packs" on the alpha download page, so langpack functioanlity can be
alpha-tested as well.
If other locales can offer langpacks that are generated from some state
of their hg tree, I also can run them through my script to inject
downloadmanager and wallet to get them working and upload them.
I don't really like having packages up that don't relate to any hg tree,
it's still possible to provide those via AMO though, of course, just
like any other add-ons.
And, as I said, no locale builds for this Alpha, we'll revisit this for
Alpha 2 and see if we're ready for those by then.
Greetings,
Robert Kaiser
Asrail
> I processed de, es-ES, fr, lt, pt-BR, ru and sk that way, as those were
> green for the first 2.0a2pre nightly, and roughly tested the langpacks
> by installing them, activating them and opening browser, add-ons manager
> and preferences (where we had the last changes) with all of them, and it
> turned out that only de, fr and lt had the last change, all others broke
> in preferences.
>
> http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0a1-candidates/build1/langpack/
> has those three langpacks and we'll have those as "experimental language
> packs" on the alpha download page, so langpack functioanlity can be
> alpha-tested as well.
>
> If other locales can offer langpacks that are generated from some state
> of their hg tree, I also can run them through my script to inject
> downloadmanager and wallet to get them working and upload them.
pt-BR updated the code today to include the changes on preferences.
I would like to have an "experimental language pack" for pt-BR.
wladow
thx
--
wladow
Robert Kaiser
> pt-BR updated the code today to include the changes on preferences.
>
> I would like to have an "experimental language pack" for pt-BR.
Thanks, done that and uploading the pack as we speak.
Robert Kaiser
Robert Kaiser
> sk is ready too, feel free to grab it ;)
Thanks, done that and uploading the pack as we speak.
Robert Kaiser
Robert Kaiser
> http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0a1-candidates/build1/langpack/
> has those three langpacks and we'll have those as "experimental language
> alpha-tested as well.
>
> If other locales can offer langpacks that are generated from some state
> of their hg tree, I also can run them through my script to inject
> downloadmanager and wallet to get them working and upload them.
> I don't really like having packages up that don't relate to any hg tree,
> it's still possible to provide those via AMO though, of course, just
> like any other add-ons.
I got that for ru, pt-BR and sk and so added them again. The list of
langpacks we'll offer as experimental work for Alpha 1 will be de, fr,
lt, pt-BR, ru and sk.
As a note to others, I won't run this on any more languages (unless you
give me a langpack you created from a state that matches 2.0a1 and some
revision of your hg, not current trunk which already went along with
more string changes).
All other languages should wait for Alpha 2, where we might try to
really have localized builds (this is more important for SeaMonkey than
Firefox or Thunderbird as we never had source-based L10n before and the
state in hg probably needs more testing because of this fact).
For now, those few langpacks give us a bit of a playground and testing
for the changed language switching code (directly in the "Appearance"
pref panel now).
Robert Kaiser