SeaMonkey and L10n: 1.0.1 / current trunk development

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

SeaMonkey and L10n: 1.0.1 / current trunk development

Robert Kaiser
Hi localizers,

I want to give a short update of things happening in the SeaMonkey
project that might affect you:

Most importantly, we're woriking on a SeaMonkey 1.0.1 release, which is
a security update in the usual style, and will be based on Gecko 1.8.0.2
and released along with Firefox and Thunderbird 1.5.0.2 releases,
currently scheduled for April 11th.

That means that SeaMonkey 1.0 language packs should work with SeaMonkey
1.0.1 and the localization itself doesn't need to be updated to work
with this new version.

We'll be shipping a number of security, stability and polishing fixes
with that release though, so we hope to get at least the same amount of
localized binaries repackaged as we already have for the current
SeaMonkey 1.0 release.

Current release candidate builds for SeaMonkey 1.0.1 are available in
ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/latest-mozilla1.8.0/
(only those builds labeled "1.0.1", of course) and should already be
identical to the release builds, unless Gecko developers, testers or us
find regressions that still need to be adressed before the release.


In other news, we don't have any major new work in the SeaMonkey 1.1a
source tree right now, so we'll not release anything to the public based
on Gecko 1.8.1alpha1 - just for your interest.


Trunk development will see some interesting changes though for those of
you who want to keep their localization up-to-date with bleeding-edge work:
I should be able to check in patches for two bugs I'm working on very
soon now, those are https://bugzilla.mozilla.org/show_bug.cgi?id=325473 
(Undo separation of language and region/content packs) and
https://bugzilla.mozilla.org/show_bug.cgi?id=328317 (merge platform .jar
files into en-US.jar).

Both of those affect L10n a lot and together have the effect of merging
all localizeable stuff into one single .jar file (compared to previously
4 files, as you know). Additionally, all language selection UI will only
have one selection then (language) instead of two (language and region).

This is the first major step in the direction of source L10n for
SeaMonkey - I'll continue working on the further needed steps once that
has landed.

At the same time, I want to encourage everyone who might be working on
SeaMonkey trunk L10n packages (I know almost noone does, but one never
knows...) to use the "new" locale codes for that work, where applicable,
just like we already do for Firefox and Thunderbird (I'll be using "de"
instead of "de-AT" for German on trunk as well). Again, this does NOT
affect SeaMonkey 1.0.x or 1.1 work, only trunk, which is currently
versioned "1.5a" internally.


And, last but not least: To everybody who does L10n work for SeaMonkey,
thanks for your work on that, we're really glad to have all of you and
to be able to provide our application in your languages!

Robert Kaiser
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: SeaMonkey and L10n: 1.0.1 / current trunk development

Ricardo Palomares Martí­nez
Robert Kaiser escribió:

>
> Trunk development will see some interesting changes though for those of
> you who want to keep their localization up-to-date with bleeding-edge work:
> I should be able to check in patches for two bugs I'm working on very
> soon now, those are https://bugzilla.mozilla.org/show_bug.cgi?id=325473
> (Undo separation of language and region/content packs) and
> https://bugzilla.mozilla.org/show_bug.cgi?id=328317 (merge platform .jar
> files into en-US.jar).
>
> Both of those affect L10n a lot and together have the effect of merging
> all localizeable stuff into one single .jar file (compared to previously
> 4 files, as you know). Additionally, all language selection UI will only
> have one selection then (language) instead of two (language and region).
>
> This is the first major step in the direction of source L10n for
> SeaMonkey - I'll continue working on the further needed steps once that
> has landed.


I suspect that work towards source L10n will, at the very least, make
us to rearrange the directory structure, as it happened with Firefox.
Am I wrong? If it will be so, then it seems better to wait at this
moment for the dust to settle, isn't it?


>
> At the same time, I want to encourage everyone who might be working on
> SeaMonkey trunk L10n packages (I know almost noone does, but one never
> knows...) to use the "new" locale codes for that work, where applicable,
> just like we already do for Firefox and Thunderbird (I'll be using "de"
> instead of "de-AT" for German on trunk as well).


...and, again, many doubts will arise about if a two-letter code is
reasonable when in the future more variants may appear. :-) I mean,
for Firefox we have es-AR and es-ES (at least) translations, but I
think that, at this moment, we only have es-ES for SeaMonkey. When
time comes to make a choice, should I drop the country code, or would
it better if I stick to es-ES, even if no more es-* localizations
appear? I *suppose* sticking to es-ES is better, specially because
toolkit l10n will be shared with Firefox and Thunderbird, but I just
want to make sure.


> And, last but not least: To everybody who does L10n work for SeaMonkey,
> thanks for your work on that, we're really glad to have all of you and
> to be able to provide our application in your languages!


Not at all. If I only could have more time to help you...

--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: SeaMonkey and L10n: 1.0.1 / current trunk development

Axel Hecht
Ricardo Palomares Martinez wrote:

> Robert Kaiser escribió:
>> Trunk development will see some interesting changes though for those of
>> you who want to keep their localization up-to-date with bleeding-edge work:
>> I should be able to check in patches for two bugs I'm working on very
>> soon now, those are https://bugzilla.mozilla.org/show_bug.cgi?id=325473
>> (Undo separation of language and region/content packs) and
>> https://bugzilla.mozilla.org/show_bug.cgi?id=328317 (merge platform .jar
>> files into en-US.jar).
>>
>> Both of those affect L10n a lot and together have the effect of merging
>> all localizeable stuff into one single .jar file (compared to previously
>> 4 files, as you know). Additionally, all language selection UI will only
>> have one selection then (language) instead of two (language and region).
>>
>> This is the first major step in the direction of source L10n for
>> SeaMonkey - I'll continue working on the further needed steps once that
>> has landed.
>
>
> I suspect that work towards source L10n will, at the very least, make
> us to rearrange the directory structure, as it happened with Firefox.
> Am I wrong? If it will be so, then it seems better to wait at this
> moment for the dust to settle, isn't it?
>
>
>> At the same time, I want to encourage everyone who might be working on
>> SeaMonkey trunk L10n packages (I know almost noone does, but one never
>> knows...) to use the "new" locale codes for that work, where applicable,
>> just like we already do for Firefox and Thunderbird (I'll be using "de"
>> instead of "de-AT" for German on trunk as well).
>
>
> ...and, again, many doubts will arise about if a two-letter code is
> reasonable when in the future more variants may appear. :-) I mean,
> for Firefox we have es-AR and es-ES (at least) translations, but I
> think that, at this moment, we only have es-ES for SeaMonkey. When
> time comes to make a choice, should I drop the country code, or would
> it better if I stick to es-ES, even if no more es-* localizations
> appear? I *suppose* sticking to es-ES is better, specially because
> toolkit l10n will be shared with Firefox and Thunderbird, but I just
> want to make sure.
>

I second this.

Axel

>
>> And, last but not least: To everybody who does L10n work for SeaMonkey,
>> thanks for your work on that, we're really glad to have all of you and
>> to be able to provide our application in your languages!
>
>
> Not at all. If I only could have more time to help you...
>
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: SeaMonkey and L10n: 1.0.1 / current trunk development

Robert Kaiser
In reply to this post by Ricardo Palomares Martí­nez
Ricardo Palomares Martinez schrieb:
> Robert Kaiser escribió:
>> This is the first major step in the direction of source L10n for
>> SeaMonkey - I'll continue working on the further needed steps once that
>> has landed.
>
> I suspect that work towards source L10n will, at the very least, make
> us to rearrange the directory structure, as it happened with Firefox.
> Am I wrong? If it will be so, then it seems better to wait at this
> moment for the dust to settle, isn't it?

Yes, it means rearranging the directory structure, but once my first two
patches are in, that won't mean too huge changes in the language packs
themselves (though it means very big changes in the source tree).

So, providing language packs for nightlies should still be possible for
those who wants to do it.
I will keep German up-to-date for sure, but of course, that will also be
the one I'll be using for testing the source-L10n patches I'll be
working on soon ;-)


>> At the same time, I want to encourage everyone who might be working on
>> SeaMonkey trunk L10n packages (I know almost noone does, but one never
>> knows...) to use the "new" locale codes for that work, where applicable,
>> just like we already do for Firefox and Thunderbird (I'll be using "de"
>> instead of "de-AT" for German on trunk as well).
>
>
> ...and, again, many doubts will arise about if a two-letter code is
> reasonable when in the future more variants may appear. :-) I mean,
> for Firefox we have es-AR and es-ES (at least) translations, but I
> think that, at this moment, we only have es-ES for SeaMonkey. When
> time comes to make a choice, should I drop the country code, or would
> it better if I stick to es-ES, even if no more es-* localizations
> appear? I *suppose* sticking to es-ES is better, specially because
> toolkit l10n will be shared with Firefox and Thunderbird, but I just
> want to make sure.

The "new" locale codes mean using what we already do for Firefox, which
is following http://wiki.mozilla.org/L10n:Simple_locale_names - that
means using two/three-letter codes for languages that don't have
different variants in different regions/countries, but still use the
region codes for those that do - and even allowing three-part locale
names where needed.

For you, that means sticking with es-ES, I'd say.


Robert Kaiser
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: SeaMonkey and L10n: 1.0.1 / current trunk development

Robert Kaiser
In reply to this post by Robert Kaiser
Robert Kaiser schrieb:
> Trunk development will see some interesting changes though for those of
> you who want to keep their localization up-to-date with bleeding-edge work:
> I should be able to check in patches for two bugs I'm working on very
> soon now, those are https://bugzilla.mozilla.org/show_bug.cgi?id=325473 
> (Undo separation of language and region/content packs) and
> https://bugzilla.mozilla.org/show_bug.cgi?id=328317 (merge platform .jar
> files into en-US.jar).

Both those bugs have been fixed today, which means that content packs
are now finally only history on trunk - and we have one common .jar file
for all localizeable resources there, which is a first major step
towards source L10n for SeaMonkey!

Robert Kaiser
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n