Re: [ANNOUNCE] SeaMonkey 2.0 OPT-IN thread
Håvard Mork
Frco. Javier Rial
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/gl/rev/a9b380bd0e72
Thanks,
Frco. Javier Rial
Pavel Franc
Hash: SHA1
> *Please opt in for this release by following up to this thread,
> referencing your locale, and the revision from your locale's
> l10n-mozilla-1.9.1 repository.*
cs opts in with
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/cs/file/7192a1e59c70
Pavel Franc
Mozilla.cz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkrKZSMACgkQebEwandxYUoZ2QCeLlzzw90U2bQLx0LfpQaVqBMv
p4oAoKoECI9nDErn8I2GoYL5dvwxdlwo
=S3hP
-----END PGP SIGNATURE-----
Joaquim Perez
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ca/file/d12b39d1e843
Thanks,
Quim
Marcelo Poli
Rimas Kudelis
2009.10.02 01:37, Robert Kaiser rašė:
> *Please opt in for this release by following up to this thread,
> referencing your locale, and the revision from your locale's
> l10n-mozilla-1.9.1 repository.*
lt opts in with:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/lt/rev/c185a8ec3337
RQ
Rail Aliev
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/tr/rev/fdb83f4b08fc
--
Rail Aliev
Siarhei
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/be/rev/943637f7f3b6
Siarhei
Niek
Dutch (nl) is opting in with:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/nl/rev/f0e288d10f2d
Niek Dekker
Kálmán „KAMI” Szalai
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/hu/file/056bad0406ea
--
Best regards,
KAMI
Kálmán „KAMI” Szalai | 神 | kami911 [at] gmail [dot] com
My projects: http://ooop.sf.net/ | http://hun.sf.net/
Blog (Hun): http://bit.ly/10ucTR | Donate: http://bit.ly/eYZO6
Follow me: http://bit.ly/gJuJZ | http://bit.ly/kDocB
Robert Kaiser
> *Please opt in for this release by following up to this thread,
> referencing your locale, and the revision from your locale's
> l10n-mozilla-1.9.1 repository.*
Opting in myself for de with
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/de/rev/12a8e00e5bb3
Robert Kaiser
Robert Kaiser
> nb-NO opting in with
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/nb-NO/file/98ed516ac8f3
Sorry, things really suck this way, but I can't take this revision due
to chatzilla just having done a change and we don't have the
infrastructure yet to clamp chatzilla down to a specific version, so
your tinderboxes are red :(
I know I need to improve that but the few of us who are doing chatzilla
need to live with the suckiness for this RC.
Robert Kaiser
Robert Kaiser
> Galician (gl) opting in with revision:
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/gl/rev/a9b380bd0e72
I'll take this for RC1, but please update
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/gl/file/a9b380bd0e72/suite/chrome/branding/brand.properties
from .add-ons.mozilla.org to .add-ons.mozilla.com, we need this change
for 2.0 final so people don't get warned about invalid certificates.
Robert Kaiser
Robert Kaiser
> cs opts in with
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/cs/file/7192a1e59c70
Sorry, things really suck this way, but I can't take this revision due
to chatzilla just having done a change and we don't have the
infrastructure yet to clamp chatzilla down to a specific version, so
your tinderboxes are red :(
I know I need to improve that but the few of us who are doing chatzilla
need to live with the suckiness for this RC.
Also, please update
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/cs/file/7192a1e59c70/suite/chrome/branding/brand.properties
from .add-ons.mozilla.org to .add-ons.mozilla.com, we need this change
wladow
--
wladow
Mozilla.sk
Dňa 02. 10. 2009 00:37, Robert Kaiser wrote / napísal(a):
> Hi localizers,
>
> Finally the time has come, the string freeze for the SeaMonkey 2.0
> series has just passed, and the string set stands as it is.
>
> Note that the about:rights / "Know Your Rights" strings are not just yet
> really accessible in the UI, this is close to landing but we checked in
> the strings already for you to work on while we're going through the
> last reviews in bug 508039. The strings are final, the code integration
> needs some last-minute polish.
>
>
> *Please opt in for this release by following up to this thread,
> referencing your locale, and the revision from your locale's
> l10n-mozilla-1.9.1 repository.*
>
>
> We expect the generation of RC1 builds right after the code freeze on
> Tuesday, October 6 at 23:59 PDT, so opt in before that if you want to be
> able to hand that candidate to your and our community for testing in
> your locale. If a few things are not 100% perfect there, it's OK, we
> know that we'll very probably do a RC2 after that, for which we expect
> everything, including locales, to be in shipping order then, though.
>
> If you don't make RC1 with your opt-in, don't be scared and opt in once
> you have things ready, as long as you're before RC2 (cut-off date
> unknown for now, I expect on Oct 13 at the earliest), you can make 2.0
> final.
> If you don't make that either, you can continue to opt-in, if there's no
> further RC for 2.0, then you will be able to make 2.0.1 a few weeks later.
>
> If you have any questions, feel free to ask them in this group.
>
> Greetings,
>
> Robert Kaiser
Robert Kaiser
I'll take this for RC1, but please update
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/nl/file/f0e288d10f2d/suite/chrome/branding/brand.properties
from .add-ons.mozilla.org to .add-ons.mozilla.com, we need this change
for 2.0 final so people don't get warned about invalid certificates.
Robert Kaiser
Robert Kaiser
> Hungarian SM2 opt-in:
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/hu/file/056bad0406ea
>
I'll take this for RC1, but please update
from .add-ons.mozilla.org to .add-ons.mozilla.com, we need this change
for 2.0 final so people don't get warned about invalid certificates.
Apart from that, everything looks good, but as a note, in
suite/profile/bookmarks.inc you changed the comment to point to your
start page instead of the actual value, so it's not used right now.
Robert Kaiser
Robert Kaiser
> We expect the generation of RC1 builds right after the code freeze on
> Tuesday, October 6 at 23:59 PDT, so opt in before that if you want to be
> able to hand that candidate to your and our community for testing in
> your locale. If a few things are not 100% perfect there, it's OK, we
> know that we'll very probably do a RC2 after that, for which we expect
> everything, including locales, to be in shipping order then, though.
Current status:
Opted in, green on dashboard and tinderbox, p12n check OK:
be ca de es-AR lt sk tr
Opted in, green on dashboard and tinderbox, p12n problem:
cs gl hu nl
- This is all only the .org->.com change, can be taken for RC1 but not
for RC2/final.
Opted in, green on dashboard but red on tinderbox:
cs nb-NO pt-PT
- This is all the late ChatZilla change, I'm somewhat to blame here as
I haven't got the build system up to pulling a specific ChatZilla
version yet. Still, we need those fixed with the current system.
Green on dashboard but not opted in:
es-ES fr pl
Red on dashboard, more than 80% localized:
ka, pt-BR, ru, sv-SE
- Please update for the missing strings and opt in!
Less than 80% localized:
ja/ja-JP-mac, ro, si
- Would be nice to see you get a localization ready for 2.0!
There is still time even for RC1, building this version might slip to
Thursday while we are awaiting patches for the worst two left blockers
to go in. If in doubt, just try opting in, if you don't make RC1, you
still can make RC2/final with the same opt-in.
Greetings,
Robert Kaiser
Adrian Kalla
Carlos Simão
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/pt-PT/rev/b119f8bdfc99
cheers
carlos
Robert Kaiser
> pt-PT opts-in with changeset
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/pt-PT/rev/b119f8bdfc99
Sorry, things really suck this way, but I can't take this revision due
to chatzilla just having done a change and we don't have the
infrastructure yet to clamp chatzilla down to a specific version, so
your tinderboxes are red :(
I know I need to improve that but the few of us who are doing chatzilla
need to live with the suckiness for this RC.
Also, please update
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/pt-PT/file/b119f8bdfc99/suite/chrome/branding/brand.properties
from .add-ons.mozilla.org to .add-ons.mozilla.com, we need this change
so people don't get warned about invalid certificates.
Robert Kaiser
Pavel Franc
> to chatzilla just having done a change and we don't have the
> infrastructure yet to clamp chatzilla down to a specific version, so
> your tinderboxes are red :(
Fixed.
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/cs/file/7192a1e59c70/suite/chrome/branding/brand.properties
> from .add-ons.mozilla.org to .add-ons.mozilla.com, we need this change
> so people don't get warned about invalid certificates.
Fixed.
Please use
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/cs/file/a86b04f8a13b
Pavel Franc
Mozilla.cz
Niek
> Niek wrote:
> > Robert,
>
> > Dutch (nl) is opting in with:
> >http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/nl/rev/f0e288d10f2d
>
> > Niek Dekker
>
> from .add-ons.mozilla.org to .add-ons.mozilla.com, we need this change
> for 2.0 final so people don't get warned about invalid certificates.
>
> Robert Kaiser
I've provided a patch and hope it will be committed on time.
Frederic Chateaux
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/fr/rev/0cc7c58c5cca
Frï¿œdï¿œric
Carlos Simão
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/pt-PT/rev/65a97544c5bc
irc was also updated
carlos
2009/10/6 Robert Kaiser <ka...@kairo.at>
Alexander L. Slovesnik
Ricardo Palomares Martínez
> Green on dashboard but not opted in:
> es-ES fr pl
I'd like to opt-in es-ES with this changeset:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/e723c92d9004
It includes latest changes in ChatZilla. However, it has been about 1
hour and a half since I comitted the changeset and tinderboxes haven't
rolled up a new build yet, so I can't promise they will turn green, sorry.
Oh, and this changeset won't include this late-l10n change in
SeaMonkey help files:
http://hg.mozilla.org/comm-central/rev/f30e72dc9092
This kind of contributions to SeaMonkey help was another reason to
skip MozCamp 09 (too many localizers that were going to be too angry
to me). ;-)
I hope to have it translated by weekend.
Best regards,
Ricardo
Mad Maks
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/nl/rev/21b9b2ea1c55
greetings
MM
Håvard Mork
> Hï¿œvard Mork wrote:
>> nb-NO opting in with
>> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/nb-NO/file/98ed516ac8f3
>
> Sorry, things really suck this way, but I can't take this revision due
> to chatzilla just having done a change and we don't have the
> infrastructure yet to clamp chatzilla down to a specific version, so
> your tinderboxes are red :(
That's OK. This is not a problem for nb-NO.
Please use the following revision for the next RC:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/nb-NO/file/5da6313a2651
Hï¿œvard
Frco. Javier Rial
> Frco. Javier Rial wrote:
> > Galician (gl) opting in with revision:
> >http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/gl/rev/a9b380bd0e72
>
> from .add-ons.mozilla.org to .add-ons.mozilla.com, we need this change
> for 2.0 final so people don't get warned about invalid certificates.
>
> Robert Kaiser
Sorry about that, fixed in:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/gl/rev/99362001eda5
Frco. Javier Rial.
Robert Kaiser
> Robert Kaiser wrote:
>> Green on dashboard but not opted in:
>> es-ES fr pl
>
>
> I'd like to opt-in es-ES with this changeset:
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/e723c92d9004
>
> It includes latest changes in ChatZilla. However, it has been about 1
> hour and a half since I comitted the changeset and tinderboxes haven't
> rolled up a new build yet, so I can't promise they will turn green, sorry.
Grr, and now it burns in venkman :(
Any chance to fix that as well?
Help not being completely current is fine, though all improvements are
welcome! :)
Robert Kaiser
Robert Kaiser
> *Please opt in for this release by following up to this thread,
> referencing your locale, and the revision from your locale's
> l10n-mozilla-1.9.1 repository.*
Another status update:
Opted in, green on dashboard and tinderbox, p12n check OK:
be ca cs de es-AR fr gl lt nb-NO nl pl pt-PT ru sk tr
Opted in, green on dashboard and tinderbox, p12n problem:
hu
- This is all only the .org->.com change, can be taken for RC1 but not
for RC2/final.
Opted in, green on dashboard but red on tinderbox:
es-ES
- This is missing strings in venkman now, which were hidden by the
ChatZilla red before but make things break now.
Red on dashboard, more than 80% localized:
ka pt-BR sv-SE
- Please update for the missing strings and opt in!
Less than 80% localized:
ja/ja-JP-mac ro si
- Would be nice to see you get a localization ready for 2.0!
I'll wait a few hours with starting RC1 builds, so that Ricardo gets a
chance to get es-ES fixed up. If you have any updates or get another
locale ready, please opt in whenever possible, RC2 (which hopefully will
equal final) will probably be done next week with the same string set,
and later 2.0.x versions will also have the same strings.
Greetings,
Robert Kaiser
Ricardo Palomares Martínez
> Opted in, green on dashboard but red on tinderbox:
> es-ES
> - This is missing strings in venkman now, which were hidden by the
> ChatZilla red before but make things break now.
>
>
> chance to get es-ES fixed up. If you have any updates or get another
> locale ready, please opt in whenever possible, RC2 (which hopefully will
> equal final) will probably be done next week with the same string set,
> and later 2.0.x versions will also have the same strings.
Although I have already answered Robert by e-mail, this is a public
confirmation that Venkman missing string has been uploaded about one
hour ago and, hopefully, all should be OK by now (except most recent
help changes).
Ricardo.
Adrian Kalla
> ka pt-BR sv-SE
> - Please update for the missing strings and opt in!
add 'it' and 'en-GB' here
'ka' is now green, but hasn't opted in...
--
Adrian Kalla
Adrian Kalla
> ka pt-BR sv-SE
> - Please update for the missing strings and opt in!
add 'it' and 'en-GB' here
Toni Hermoso Pulido
I was trying to get a opt-in, but I've seen I don't have neither
Venkman nor ChatZilla translated interfaces in l10n nightlies.
I realised that compare-locales command I used against suite l10n.ini
do not check them by default.
As far as I have seen, all-locales files of these extensions do not
seem to have 'ca' locale included.
What should I do?
Thanks in advance!
2009/10/2 Robert Kaiser <ka...@kairo.at>:
> Hi localizers,
>
> Finally the time has come, the string freeze for the SeaMonkey 2.0 series
> has just passed, and the string set stands as it is.
>
> Note that the about:rights / "Know Your Rights" strings are not just yet
> really accessible in the UI, this is close to landing but we checked in the
> strings already for you to work on while we're going through the last
> reviews in bug 508039. The strings are final, the code integration needs
> some last-minute polish.
>
>
> *Please opt in for this release by following up to this thread,
> referencing your locale, and the revision from your locale's
> l10n-mozilla-1.9.1 repository.*
>
>
> We expect the generation of RC1 builds right after the code freeze on
> Tuesday, October 6 at 23:59 PDT, so opt in before that if you want to be
> able to hand that candidate to your and our community for testing in your
> locale. If a few things are not 100% perfect there, it's OK, we know that
> we'll very probably do a RC2 after that, for which we expect everything,
> including locales, to be in shipping order then, though.
>
> If you don't make RC1 with your opt-in, don't be scared and opt in once you
> have things ready, as long as you're before RC2 (cut-off date unknown for
> now, I expect on Oct 13 at the earliest), you can make 2.0 final.
> If you don't make that either, you can continue to opt-in, if there's no
> further RC for 2.0, then you will be able to make 2.0.1 a few weeks later.
>
> If you have any questions, feel free to ask them in this group.
>
--
Toni Hermoso Pulido
http://www.cau.cat
Adrian Kalla
> Hi Robert,
>
> I was trying to get a opt-in, but I've seen I don't have neither
> Venkman nor ChatZilla translated interfaces in l10n nightlies.
> I realised that compare-locales command I used against suite l10n.ini
> do not check them by default.
> As far as I have seen, all-locales files of these extensions do not
> seem to have 'ca' locale included.
> What should I do?
Please open bugs similar to the following ones:
https://bugzilla.mozilla.org/show_bug.cgi?id=470625
https://bugzilla.mozilla.org/show_bug.cgi?id=484301
https://bugzilla.mozilla.org/show_bug.cgi?id=502445
--
Adrian Kalla
Robert Kaiser
> We expect the generation of RC1 builds right after the code freeze on
> Tuesday, October 6 at 23:59 PDT, so opt in before that if you want to be
> able to hand that candidate to your and our community for testing in
> your locale.
Here's the RC1 status:
Opted in, green on dashboard and tinderbox, p12n check OK:
be ca cs de es-ES es-AR fr gl lt nb-NO nl pl pt-PT ru sk tr
Opted in, green on dashboard and tinderbox, p12n problem:
hu
- This is all only the .org->.com change, can be taken for RC1 but not
for RC2/final.
----- The locales above this line are in RC1 -----
Not opted but green on dashboard:
ka
- Opt-in for RC2 is possible, of course, I have done a rough p12n
check and there are redundant .src and .png files in searchplugins,
which should be removed, they are pulled in from en-US if not
existent.
Red on dashboard, more than 80% localized:
it pt-BR sv-SE
- Please update for the missing strings and opt in!
Less than 80% localized:
en-GB ja/ja-JP-mac ro si
- Would be nice to see you get a localization ready for 2.0!
- en-GB is of course a special case int that it can opt in with a lot
of unchanged strings, after all, en-US and en-GB do have a lot of
similarities.
If you have any updates or get another locale ready, please opt in
whenever possible, RC2 (which hopefully will equal final) will probably
be done next week with the same string set, and later 2.0.x versions
will also have the same strings.
That said, RC1 builds have been started with the 17 locales mentioned
above, builds are available at
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0rc1-candidates/build1/
and we'd be happy if you could help us test those builds as we want to
move them public very fast.
Greetings,
Robert Kaiser
Toni Hermoso Pulido
https://bugzilla.mozilla.org/show_bug.cgi?id=521385
Sorry if answered before, translated DOM inspector is going to be
shipped as well?
Thanks.
2009/10/8 Adrian Kalla <aka...@aviary.pl>:
--
Kálmán „KAMI” Szalai
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/hu/file/47de448e1a43
I will review bookmarks.inc soon.
KAMI
Robert Kaiser írta:
> Kálmán „KAMI” Szalai wrote:
>> Hungarian SM2 opt-in:
>>
>> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/hu/file/056bad0406ea
>>
>
>
> I'll take this for RC1, but please update
> from .add-ons.mozilla.org to .add-ons.mozilla.com, we need this change
> for 2.0 final so people don't get warned about invalid certificates.
>
> Apart from that, everything looks good, but as a note, in
> suite/profile/bookmarks.inc you changed the comment to point to your
> start page instead of the actual value, so it's not used right now.
>
> Robert Kaiser
>
>
--
Best regards,
KAMI
Kálmán „KAMI” Szalai | 神 | kami911 [at] gmail [dot] com
My projects: http://ooop.sf.net/ | http://hun.sf.net/
Blog (Hun): http://bit.ly/10ucTR | Donate: http://bit.ly/eYZO6
Follow me: http://bit.ly/gJuJZ | http://bit.ly/kDocB
Robert Kaiser
> Done:
> https://bugzilla.mozilla.org/show_bug.cgi?id=521385
> Sorry if answered before, translated DOM inspector is going to be
> shipped as well?
Yes, but that totally depends on the dom-inspector itself, the locales
for it are in its own repository right now.
Robert Kaiser
Giasher
wladow
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/sk/file/51a2b0a8058a
--
wladow
Mozilla.sk
Dňa 06. 10. 2009 21:22, wladow wrote / napísal(a):
> sk: http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/sk/file/37ef255c2627
>
> --
> wladow
> Mozilla.sk
>
Peter Kihlstedt
> Red on dashboard, more than 80% localized:
> it pt-BR sv-SE
> - Please update for the missing strings and opt in!
>
>
> If you have any updates or get another locale ready, please opt in
> whenever possible, RC2 (which hopefully will equal final) will probably
> be done next week with the same string set, and later 2.0.x versions
> will also have the same strings.
>
Here is the opt-in message for sv-SE
And the link is:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/sv-SE/rev/3557240b3d1e
Regards
Peter
Ricardo Palomares Martínez
> *Please opt in for this release by following up to this thread,
> referencing your locale, and the revision from your locale's
> l10n-mozilla-1.9.1 repository.*
>
> Tuesday, October 6 at 23:59 PDT, so opt in before that if you want to be
> able to hand that candidate to your and our community for testing in
> know that we'll very probably do a RC2 after that, for which we expect
> everything, including locales, to be in shipping order then, though.
>
> If you don't make RC1 with your opt-in, don't be scared and opt in once
> you have things ready, as long as you're before RC2 (cut-off date
> unknown for now, I expect on Oct 13 at the earliest), you can make 2.0
> final.
Hi, Robert, could you use this changeset for RC2?
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/035e7f2efbf8
Still, depending of the actual RC2 cut-off date, I could provide
another changeset later removing some duplicate accesskeys.
TIA
Rimas Kudelis
> Hi Robert,
>
> 2009.10.02 01:37, Robert Kaiser rašė:
>> *Please opt in for this release by following up to this thread,
>> referencing your locale, and the revision from your locale's
>> l10n-mozilla-1.9.1 repository.*
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/lt/rev/c185a8ec3337
Update: I've just copied fresh English help files to my tree. Please use
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/lt/rev/66029a6acff4
from now on.
Rimas
Alexander L. Slovesnik
07.10.2009 02:27 you wrote:
> ru opts in:
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ru/rev/2c31aee6b840
>
Updated rev. for RC2 with several RC1 fixes:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ru/rev/4c3c3f610eff
--
Sincerely yours,
Alexander L. Slovesnik a.k.a. Unghost
==>Web-page: http://www.unghost.ru/
==>Jabber ID: ung...@mozilla-russia.org
==>Gmail Talk ID: ung...@gmail.com
==>IRC: irc://irc.mozilla.org/mozilla-ru
Toni Hermoso Pulido
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ca/rev/64320205dfcf
2009/10/2 Robert Kaiser <ka...@kairo.at>:
> Hi localizers,
>
> Finally the time has come, the string freeze for the SeaMonkey 2.0 series
> has just passed, and the string set stands as it is.
>
> Note that the about:rights / "Know Your Rights" strings are not just yet
> really accessible in the UI, this is close to landing but we checked in the
> strings already for you to work on while we're going through the last
> reviews in bug 508039. The strings are final, the code integration needs
> some last-minute polish.
>
>
> *Please opt in for this release by following up to this thread,
> referencing your locale, and the revision from your locale's
> l10n-mozilla-1.9.1 repository.*
>
>
> We expect the generation of RC1 builds right after the code freeze on
> Tuesday, October 6 at 23:59 PDT, so opt in before that if you want to be
> able to hand that candidate to your and our community for testing in your
> locale. If a few things are not 100% perfect there, it's OK, we know that
> we'll very probably do a RC2 after that, for which we expect everything,
> including locales, to be in shipping order then, though.
>
> If you don't make RC1 with your opt-in, don't be scared and opt in once you
> have things ready, as long as you're before RC2 (cut-off date unknown for
> now, I expect on Oct 13 at the earliest), you can make 2.0 final.
> If you don't make that either, you can continue to opt-in, if there's no
> further RC for 2.0, then you will be able to make 2.0.1 a few weeks later.
>
> If you have any questions, feel free to ask them in this group.
>
--
Siarhei
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/be/rev/51ab81bdc9f4
Siarhei
Ricardo Palomares Martínez
> Hi, Robert, could you use this changeset for RC2?
>
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/035e7f2efbf8
>
>
> Still, depending of the actual RC2 cut-off date, I could provide
> another changeset later removing some duplicate accesskeys.
Not much, but some changes in accesskeys for SeaMonkey that I'd like
to see for RC2 if possible:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/55936388a84d
TIA
Cédric Corazza
> fr is opting in with revision :
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/fr/rev/0cc7c58c5cca
>
> Frï¿œdï¿œric
Well, I'm opting-in with a new patchset for the French locale as I've
just noticed that the final cut is for tomorrow (well today) morning,
and since the last opt-in, many fixes have been pushed. I couldn't
contact my team mates as they are sleeping right now, but I guess this
is the right move.
http://hg.mozilla.org/l10n-central/fr/rev/4d743c279ce1
Cï¿œdric
Robert Kaiser
> Well, I'm opting-in with a new patchset for the French locale as I've
> just noticed that the final cut is for tomorrow (well today) morning,
> and since the last opt-in, many fixes have been pushed. I couldn't
> contact my team mates as they are sleeping right now, but I guess this
> is the right move.
>
> http://hg.mozilla.org/l10n-central/fr/rev/4d743c279ce1
You need to opt in with a l10n-mozilla-1.9.1 changeset, not a
l10n-central one...
Robert Kaiser
Benoit
Hi Robert,
The correct changeset is indeed the last one on the 1.9.1 branch:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/fr/rev/95ac7a019de4
Thanks!
--
Benoit
FrenchMozilla l1n team
Adrian Kalla
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/pl/rev/7f3f177f8076
Robert Kaiser
> Georgian (ka) http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ka/rev/73a673cf5229,
> please
We're taking it, but for the future, please remove the .png and .src
files in
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ka/file/73a673cf5229/suite/searchplugins
- if they don't exist but are in the list.txt, we pull in the ones with
the same name from en-US.
Robert Kaiser
Robert Kaiser
> Here is the opt-in message for sv-SE
>
> And the link is:
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/sv-SE/rev/3557240b3d1e
Hrm,
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/sv-SE/file/3557240b3d1e/suite/chrome/branding/brand.properties
has the .add-ons.mozilla.org URLs that cause certificate errors, please
change those to .add-ons.mozilla.com - I don't feel very good with
shipping an official version that triggers certificate errors in its
internal links :(
Robert Kaiser
Frederic Chateaux
If it is not too late, I'd like you use this revision
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/fr/rev/2d7746daeb44
for fr.
Unless, it-'l be in 2.0.1.
Frédéric
Ricardo Palomares Martínez
I've noticed an accesskey that it is not honored in L10n:
Despite having an "v", I see "(T)", corresponding to the en-US
original. The string can be seen in Mail & News, View menu, Layout
option, "Thread pane" sub-option.
Pascal is going to kill me if I'm not 4 Km. from my home in 15
minutes, :-) so I can't file the bug right now, I'll do it tonight if
nobody else do it before.
Best regards,
Ricardo
Toni Hermoso Pulido
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ca/rev/bc3d9543daae
Take this for RC2.
Thanks!
2009/10/13 Toni Hermoso Pulido <ton...@softcatala.cat>:
Hasse
Thanks for finding this. Fixed in changeset:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/sv-SE/rev/504de5fc23b8
--
Hasse
sv-SE l10n team
Adrian Kalla
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/pl/rev/4eecd26320ba
Robert Kaiser
> If you don't make RC1 with your opt-in, don't be scared and opt in once
> you have things ready, as long as you're before RC2 (cut-off date
> unknown for now, I expect on Oct 13 at the earliest), you can make 2.0
> final.
RC2 was started with the following opted-in locales and versions:
be 51ab81bdc9f4
ca bc3d9543daae
cs a86b04f8a13b
de bbe53004bc33
es-AR ffaf6f74129c
es-ES 55936388a84d
fr 2d7746daeb44
gl 99362001eda5
hu 47de448e1a43
ka 73a673cf5229
lt 66029a6acff4
nb-NO 5da6313a2651
nl 21b9b2ea1c55
pl 4eecd26320ba
pt-PT 65a97544c5bc
ru 4c3c3f610eff
sk 51a2b0a8058a
sv-SE 504de5fc23b8
tr fdb83f4b08fc
tr will be listed as beta/unofficial on the download page as it's not
completely ready for a final yet (but leaving users stranded on RC1 also
seems like a bad idea).
Any further opt-in will count for 2.0.1 unless we need to do yet another
release candidate for 2.0, which we hope will not happen.
Robert Kaiser
Alexander L. Slovesnik
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ru/rev/d1cc30f27d1b
Ricardo Palomares Martínez
>
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/035e7f2efbf8
>
Hummm... It seems that this changeset didn't make it into RC2 (I'd
swear I posted it before the cut-off deadline for RC2, on 20091013
22:41 GMT). I guess it is now too late to have it for SM2.0 final; the
bad thing is that it contained the help contents on Add-on Manager. :-(
BTW, I can't access es-ES Mercurial repository in the above URL, but
the server itself works. It is as if the locale repositories had
dissapeared (or changed their names).
Robert Kaiser
> Ricardo Palomares Martínez escribió:
>> Hi, Robert, could you use this changeset for RC2?
>>
>>
>> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/035e7f2efbf8
>>
>
>
> Hummm... It seems that this changeset didn't make it into RC2 (I'd
> swear I posted it before the cut-off deadline for RC2, on 20091013
> 22:41 GMT). I guess it is now too late to have it for SM2.0 final; the
> bad thing is that it contained the help contents on Add-on Manager. :-(
You posted another revision on 14th and I used that one.
> BTW, I can't access es-ES Mercurial repository in the above URL, but
> the server itself works. It is as if the locale repositories had
> dissapeared (or changed their names).
Unfortunately, because of this current brokenness, I can't check the
version history and what did or could have gone wrong here.
Robert Kaiser
Ricardo Palomares Martínez
>
> You posted another revision on 14th and I used that one.
Oh, yes, I didn't mention it because I thought that was late. :-)
>> BTW, I can't access es-ES Mercurial repository in the above URL, but
>> the server itself works. It is as if the locale repositories had
>> dissapeared (or changed their names).
>
> Unfortunately, because of this current brokenness, I can't check the
> version history and what did or could have gone wrong here.
Yeah, if it can't make 2.0.0, it will make 2.0.1. :-) Anyway, I'm
doing some cleanup and will provide further changeset(s).
Ricardo
Robert Kaiser
>>
>> You posted another revision on 14th and I used that one.
>
> Oh, yes, I didn't mention it because I thought that was late. :-)
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/pushloghtml
tells me that the SEAMONKEY_2_0rc2_RELEASE tag is indeed on the lastest
changeset from you on the default branch - doesn't look like there's
anything in the repository that didn't make the RC2 and therefore the
final (if everything goes well).
> Yeah, if it can't make 2.0.0, it will make 2.0.1. :-) Anyway, I'm
> doing some cleanup and will provide further changeset(s).
Sure, any further changesets being posted here will make 2.0.1.
Robert Kaiser
文少华
zh-CN just commited initial translation for Suite, Could you please help
to add zh-CN sea20x to the l10n dashboard?
We'll do more verifications/corrections to this initial translation to
catch up.
BR.
Holy
On Fri, Oct 2, 2009 at 6:37 AM, Robert Kaiser <ka...@kairo.at> wrote:
> Hi localizers,
>
> Finally the time has come, the string freeze for the SeaMonkey 2.0 series
> has just passed, and the string set stands as it is.
>
> Note that the about:rights / "Know Your Rights" strings are not just yet
> really accessible in the UI, this is close to landing but we checked in the
> strings already for you to work on while we're going through the last
> reviews in bug 508039. The strings are final, the code integration needs
> some last-minute polish.
>
>
> *Please opt in for this release by following up to this thread,
> referencing your locale, and the revision from your locale's
> l10n-mozilla-1.9.1 repository.*
>
>
> We expect the generation of RC1 builds right after the code freeze on
> Tuesday, October 6 at 23:59 PDT, so opt in before that if you want to be
> able to hand that candidate to your and our community for testing in your
> locale. If a few things are not 100% perfect there, it's OK, we know that
> we'll very probably do a RC2 after that, for which we expect everything,
> including locales, to be in shipping order then, though.
>
> If you don't make RC1 with your opt-in, don't be scared and opt in once you
> have things ready, as long as you're before RC2 (cut-off date unknown for
> now, I expect on Oct 13 at the earliest), you can make 2.0 final.
> If you don't make that either, you can continue to opt-in, if there's no
> further RC for 2.0, then you will be able to make 2.0.1 a few weeks later.
>
> If you have any questions, feel free to ask them in this group.
>
> Greetings,
>
> Robert Kaiser
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>
Carlos Simão
just committed a new changeset to correct some minor accesskey errors and
typos correction.
changeset:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/pt-PT/rev/ce729d49d246
Robert Kaiser
> Hi Robert,
> zh-CN just commited initial translation for Suite, Could you please help
> to add zh-CN sea20x to the l10n dashboard?
> We'll do more verifications/corrections to this initial translation to
> catch up.
Please file a bug report in SeaMonkey - Build Config to be added to
all-locales. Once that's done, it will show up on dashboard automatically.
Thanks a lot for working on this localization!
Robert Kaiser
Robert Kaiser
> Updated rev. for final with several fixes:
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ru/rev/d1cc30f27d1b
As long as we don't do another release candidate, 2.0 final is closed
already, but we'll take this one for 2.0.1.
Robert Kaiser
Frederic Chateaux
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/fr/rev/194f11214a7a
for finale release.
Unless, it will be for 2.0.1.
Thanks.
Frédéric
Ricardo Palomares Martínez
> *Please opt in for this release by following up to this thread,
> referencing your locale, and the revision from your locale's
> l10n-mozilla-1.9.1 repository.*
Hi, Robert, could you please use this changeset for SeaMonkey 2.0.1 es-ES?
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/aa11673fc1f0
BTW, it includes help content updated in bug 232054 [1] which is about
to land into comm-1.9.1. It means that L10n teams keeping SM help up
to date will need to update their mail_help.xhtml file (not a big
change, don't worry!) :-) and ask for a new changeset, too.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=232054
TIA
Ricardo
Ricardo Palomares Martínez
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/aa11673fc1f0
>
While reviewing Thunderbird 3, I've come also to a number of fixes for
SeaMonkey 2.0.1, latest of which are in this changeset:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/0841d490a289
Thank you.
Ricardo Palomares Martínez
> SeaMonkey 2.0.1, latest of which are in this changeset:
>
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/0841d490a289
Sorry to introduce so many noise, but can I propose this changeset
instead?
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/c2053dd61b7b
Thank you.
Mad Maks
> Op 10/06/2009 11:52 PM, Niek schreef:
>> On Oct 6, 9:26 pm, Robert Kaiser<ka...@kairo.at> wrote:
>>> Niek wrote:
>>>> Robert,
>>>
>>>> Dutch (nl) is opting in with:
>>>> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/nl/rev/f0e288d10f2d
>>>
>>>> Niek Dekker
>>>
>>> I'll take this for RC1, but please
>>> updatehttp://hg.mozilla.org/releases/l10n-mozilla-1.9.1/nl/file/f0e288d10f2...
>>>
>>> from .add-ons.mozilla.org to .add-ons.mozilla.com, we need this change
>>> for 2.0 final so people don't get warned about invalid certificates.
>>>
>>> Robert Kaiser
>>
>> I've provided a patch and hope it will be committed on time.
>
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/nl/rev/21b9b2ea1c55
>
> greetings
>
> MM
new changeset for 2.0.1 (thunderbird 3 patches applied on mailnews)
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/nl/rev/58af73bd44f2
thanks
MM
Rimas Kudelis
> Rimas Kudelis rašė:
>> Hi Robert,
>>
>> 2009.10.02 01:37, Robert Kaiser rašė:
>>> *Please opt in for this release by following up to this thread,
>>> referencing your locale, and the revision from your locale's
>>> l10n-mozilla-1.9.1 repository.*
>>
>> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/lt/rev/c185a8ec3337
>
> Update: I've just copied fresh English help files to my tree. Please use
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/lt/rev/66029a6acff4
> from now on.
Another update here:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/lt/rev/5b66aae66f8a
Please use that in future.
Rimas
Ricardo Palomares Martínez
> instead?
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/c2053dd61b7b
Some changes in ChatZilla files (does it still apply to 1.9.1?):
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/023d0d153ade
although last changeset now is this (a couple of changes in
Thunderbird files):
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/05a57b23bce4
TIA
ytooyama
The localize of "SeaMonkey2 -ja (Japanese)" was able to be packed.
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ja
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ja/file/8281c55f3533
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ja-JP-mac
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ja-JP-mac/file/fe0aa41d5573
Please use this changeset for "ja" and "ja-JP-Mac" in SeaMonkey 2.0.1
releases:
Thank you.
Rimas Kudelis
Ricardo Palomares Martínez
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/023d0d153ade
>
> although last changeset now is this (a couple of changes in
> Thunderbird files):
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/05a57b23bce4
I don't really know if we should wait for a SM 2.0.1 thread, but could
I propose this changeset for next update release?
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/cff8b9d201c3
Actually, it goes back so far to this other changeset:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/3311ccc1de42
which is the last making changes to files used by SeaMonkey.
TIA
wladow
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/sk/file/6bf97a76147a
--
wladow
Mozilla.sk
Dňa 12. 10. 2009 20:49, wladow wrote / napísal(a):
> Updated rev. for RC2 with several RC1 feedback fixes and help update
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/sk/file/51a2b0a8058a
>
> --
> wladow
> Mozilla.sk
>
> Dňa 06. 10. 2009 21:22, wladow wrote / napísal(a):
>> sk:
>> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/sk/file/37ef255c2627
>>
>> --
>> wladow
>> Mozilla.sk
>>
Giacomo Magnini
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/it/file/c4476bfd1e40
Still missing:
- Extensions (bug open)
- Some online guide
Ciao, Giacomo.
Robert Kaiser
That's OK, both are optional, actually.
Robert Kaiser
Robert Kaiser
Sorry, I can't add them in their current state.
Both are red on tinderbox due to ChatZilla L10n being activated for them
but incomplete, see the "SeaMonkey comm-1.9.1" columns on
http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-ja and
http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-ja-JP-mac
Once those are fixed, we can get you added, but as we're about to spin
2.0.1, that probably will only be for 2.0.2, then.
Robert Kaiser
Robert Kaiser
> Opting in myself for de with
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/de/rev/12a8e00e5bb3
For documentation, updating de opt-in to
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/de/rev/d1bdeb0764a5
for 2.0.1 release.
Robert Kaiser
Robert Kaiser
(SEAMONKEY_2_0_RELEASE means the exact same revision 2.0 shipped with
and therefore has this tag set):
be SEAMONKEY_2_0_RELEASE
ca SEAMONKEY_2_0_RELEASE
cs SEAMONKEY_2_0_RELEASE
de d1bdeb0764a5
es-AR SEAMONKEY_2_0_RELEASE
es-ES 3311ccc1de42
fr 194f11214a7a
gl SEAMONKEY_2_0_RELEASE
hu SEAMONKEY_2_0_RELEASE
it c4476bfd1e40
ka SEAMONKEY_2_0_RELEASE
lt 8d717617ada9
nb-NO SEAMONKEY_2_0_RELEASE
nl 58af73bd44f2
pl SEAMONKEY_2_0_RELEASE
pt-PT ce729d49d246
ru d1cc30f27d1b
sk 6bf97a76147a
sv-SE SEAMONKEY_2_0_RELEASE
tr SEAMONKEY_2_0_RELEASE
We welcome it as a new addition to SeaMonkey 2.0.x!
Any further opt-ins will be taken for 2.0.2, currently scheduled for
early February of 2010.
Robert Kaiser
Robert Kaiser
> Actually, it goes back so far to this other changeset:
>
> http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/3311ccc1de42
>
> which is the last making changes to files used by SeaMonkey.
Ouch. Your locale failed in the release automation because of ChatZilla
not matching the version we ship in 2.0.x, and indeed
http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-es-ES is
also red for comm-1.9.1.
I wonder what to do now, in the worst case we can't ship es-ES in 2.0.1 :(
Robert Kaiser
Ricardo Palomares Martínez
> Ricardo Palomares Martínez schrieb:
Humm... I forgot to update the import directory in MT when
comm-central branched.
However, I've fixed it, updated comm-1.9.1 with python client.py
checkout, upated ChatZilla in MT (with no apparent changes) and
exported it to my local copy of l10n-mozilla1.9.1/es-ES.
And, after that, compare-locales.pl doesn't find any differences
between my local copies of en-US and es-ES, and hg stat doesn't find
any pending changes. Am I using the right paths for compare-locales.pl
(I think so)?
$ compare-locales.pl
comm-1.9.1/mozilla/extensions/irc/locales/en-US/chrome/
l10n-mozilla1.9.1-es-ES/extensions/irc/chrome/
In other words, is client.py checkout in comm-1.9.1 working right?
I want a SM 2.0.1 es-ES update, too. O:-)
TIA
Robert Kaiser
> checkout, upated ChatZilla in MT (with no apparent changes) and
> exported it to my local copy of l10n-mozilla1.9.1/es-ES.
Then that is probably why you fail. You should have no different
ChatZilla strings than in 2.0 final (in terms of IDs, correcting L10n
problems is fine).
> And, after that, compare-locales.pl doesn't find any differences
> between my local copies of en-US and es-ES, and hg stat doesn't find
> any pending changes. Am I using the right paths for compare-locales.pl
> (I think so)?
>
> $ compare-locales.pl
> comm-1.9.1/mozilla/extensions/irc/locales/en-US/chrome/
> l10n-mozilla1.9.1-es-ES/extensions/irc/chrome/
Correct if you use the right checkout (which is probably where you fail).
> In other words, is client.py checkout in comm-1.9.1 working right?
No. client.py checkout retrieves the _current_ chatzilla, while we are
actually using the one from when 2.0 was shipped, i.e. the state of
"2009-10-14 00:00" (time zone should not matter much).
> I want a SM 2.0.1 es-ES update, too. O:-)
Would be nice, but we need to be fast in correcting that...
Robert Kaiser
Ricardo Palomares Martínez
> Ricardo Palomares Martínez schrieb:
>
> No. client.py checkout retrieves the _current_ chatzilla, while we are
> actually using the one from when 2.0 was shipped, i.e. the state of
> "2009-10-14 00:00" (time zone should not matter much).
Humm... I'd say that client.py is failing, then. I mean, client.py
checkout is supposed to be the command to use in order to have
comm-1.9.1 up to date, which is still needed for Calendar 1.0b1 (and
it could happen for the other comm-1.9.1 apps, too, if for instance
fixing a security problem involved changes in strings; it is rare that
string freeze is broken, but I think it has hapenned in the past).
>> I want a SM 2.0.1 es-ES update, too. O:-)
>
> Would be nice, but we need to be fast in correcting that...
I've pushed a chatzilla.properties that should fix the tinderboxes
(I've kept some QA fixes I did). Still, we should think about the
client.py checkout issue... Maybe it should be modified so no
chatzilla, venkman, etc. is done, and instead a frozen copy of those
strings is created in mozilla1.9.1?
TIA
Ricardo Palomares Martínez
> (I've kept some QA fixes I did).
We're green again. :-) I hope we can be included in SeaMonkey 2.0.1
release.
Best regards.
Ricardo Palomares Martínez
> Ricardo Palomares Martínez schrieb:
>> (I've kept some QA fixes I did).
>
> whole build process on Sunday, taking a new es-ES version (you didn't
> state one here, right?) and hoping everything is fine then.
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/1fc7ce5d4fa1
I've checked in a newline in defines.inc in order to force a new
build, and once I've seen green tinderboxes, I've backed it out.
> BTW, any other application being released from comm-1.9.1 as well is no
> argument by itself, as no other application bundles any of those
> extensions by default.
That's true. What I mean is that we have got used to "python client.py
checkout" as the update command to get our comm-1.9.1 and comm-central
repository copies up to date, no other instructions have been given
here, and we expect that every change happening by using that command
is legimitate.
I truly think that the best solution implies keeping the current
habits (not only because it is more convenient for localizers, but
also because it saves editing documentation to reflect any hypotetical
changes in procedure). I don't know if it is possible at all due to
policies in the repositories, but could a snapshot of CVS-imported
strings be created in comm-1.9.1, and a modification in client.py done
so, instead of importing those strings from CVS to
mozilla/extensions/... they get copied from the snapshot directory?
Something like:
comm-1.9.1
+--build
+--calendar
(...)
+-snapshots
| +--irc
| +--venkman
(...)
\--suite
client.py checkout should copy from that snapshot to cloned
mozilla/extensions/ thus ensuring the correct strings are used. Maybe
it is not as simple as I depict it, but if it is, it should work. :-)
(Disclaimer: I don't know Python, so I can't provide a patch).
> We know that th whole situation around extensions is not ideal right
> now, and we are only over time getting a view of how to deal with them
> best - sorry for inconveniences that may cause.
> We think ensuring a string freeze over the SeaMonkey 2.0.x series is
> important in any case, so that is one of the fixed points in there which
> you can count on.
OK, so my import path in MT (using comm-central) was right, after all. :-)
This also answer a question I had pending. I was waiting for you to
recover from your holidays to ask if remaining bugs related to
updating en-US help contents for SeaMonkey so it matches UI were still
wanted for SM 2.0.x, but I guess they are not, since it would break
string freeze. :-?
Best regards
Robert Kaiser
Thanks, will use that one in a build 2 for 2.0.1, then we should be gren
on all 20 locales, I hope :)
> I truly think that the best solution implies keeping the current
> habits (not only because it is more convenient for localizers, but
> also because it saves editing documentation to reflect any hypotetical
> changes in procedure). I don't know if it is possible at all due to
> policies in the repositories, but could a snapshot of CVS-imported
> strings be created in comm-1.9.1, and a modification in client.py done
> so, instead of importing those strings from CVS to
> mozilla/extensions/... they get copied from the snapshot directory?
That would be much more complicated than just making client.py pull a
specific version by default (once chatzilla is being pulled from hg).
> This also answer a question I had pending. I was waiting for you to
> recover from your holidays to ask if remaining bugs related to
> updating en-US help contents for SeaMonkey so it matches UI were still
> wanted for SM 2.0.x, but I guess they are not, since it would break
> string freeze. :-?
Help updates are OK, as they don't break any compiling or such, and a
number of locales don't have fully localized help anyhow.
Robert Kaiser
Alexander L. Slovesnik
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ru/rev/e1fc739a2faa
--
Sincerely yours,
Alexander L. Slovesnik a.k.a. Unghost
==>Web-page: http://www.unghost.ru/
==>Jabber ID: ung...@mozilla-russia.org
==>Gmail Talk ID: ung...@gmail.com
==>IRC: irc://irc.mozilla.org/mozilla-ru
ytooyama
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ja/rev/ba473f40acb4
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ja-JP-mac/rev/df1f7ce45870
Please use this changeset for "ja" and "ja-JP-Mac" in SeaMonkey 2.0.2
releases:
Thanks.
Toni Hermoso Pulido
> Hi localizers,
New revision for ca:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ca/rev/dab54aff0e15
--
Toni Hermoso Pulido
http://www.cau.cat
Siarhei
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/be/rev/975bf2bd4d94
With best regards,
Siarhei
Ricardo Palomares Martínez
A new changeset for SeaMonkey 2.0.2:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/d4b04d36deb2
There is a later changeset, which only removes some obsolete calendar
files:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/rev/e70c20ea47b3
Thanks in advance, and have a happy new year. :-)
Rail Aliev
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/tr/rev/5c08da56496d
--
Rail Aliev