We're getting geared up to do another Firefox update, Firefox 1.0.2, and to do our first Thunderbird update -- which will also be called 1.0.2, just to keep things in sync. Those releases are scheduled to happen very soon, but there are no changes required from the L10N teams.
We simply need you all to test the Firefox 1.0.2 builds because, like 1.0.1, we're not allowing any changes in (we did take a change to update the copyright date). We'll announce here when the Firefox 1.0.2 localization builds are ready for testing. When you've tested your build, you'll note that it's ready for shipping in the Firefox 1.0.2 localization bug <https://bugzilla.mozilla.org/show_bug.cgi?id=286605>.
For Thunderbird 1.0.2, we're also requiring that no further changes be made to the localizations as this is just a security update and not a full release. We'll let you know what the final build is so you all can use that as the base for your localization. When your build is completed, you'll comment in the Thunderbird 1.0.2 bug <https://bugzilla.mozilla.org/show_bug.cgi?id=286606> saying that it's ready for shipping and giving a URL where Chase can find the package(s).
For Mozilla 1.7.6, the process is the same as it was for Mozilla 1.5. We'll let you know when we've completed the en-US builds so you all can use that as the base for your localizations. The MLP will handle posting those those builds.
If I've got anything wrong here, Chase, Kairo, or Axel will correct me.
Hello All, Me and my team is working on FireFox translation. But we are very sad to see no Bengali/Bangla language option options in both Fonts and Language options. As you guys are discussing on next 1.0.2 release, so is it possible to add Bengali language in Mozilla products?
> I know you say we should not make any change to language resource, but > your en-US have some diff and we should do same as yours I think. > Concerning adding entity about XSLT update is not needed but I think we > should change 'copyrightText' since copyright should be same as yours. > We shouldn't neglect notice of copyright. > # Years of copyright was '1998-2004' in 1.0 but now '1998-2005'. > # I attach the en-US-mail.jar contents' diff between 1.0 final and > # 20030317 build (1.0.2RC), see it for details.
> To fix these diff same as en-US one has no risk to introduce other bugs > and it will take only few minutes. I think l10n team should fix these > diff (only these, without typo/translation fix as you require).
> Please give us a approval to fix only these diff same as en-US one.
date: 2005/03/17 01:22:10; author: cmp%mozilla.org; state: Exp; lines: +1 -1 Land attachment 177670 from bug 278936 to bump the year in the about dialog to 2005 for the locales receiving the check-in.
This is the german log, Chase did update the copyright notice for all locales himself.
If your locale has no update to browser/locale/ab-CD/chrome/browser/aboutDialog.dtd, yell.
>> Please give us a approval to fix only these diff same as en-US one.
> date: 2005/03/17 01:22:10; author: cmp%mozilla.org; state: Exp; lines: > +1 -1 > Land attachment 177670 from bug 278936 to bump the year in the about > dialog to 2005 for the locales receiving the check-in.
> This is the german log, Chase did update the copyright notice for all > locales himself.
> If your locale has no update to > browser/locale/ab-CD/chrome/browser/aboutDialog.dtd, yell.
umm.. dynamis was talking about Thunderbird... the whole message through. Chase would find it mighty difficul to update Thunderbird locales (other than en-US) AFAIK.
To reiterate: Is it ok to do the same changes in non en-US Thunderbirds as has already been made to en-US (changes to copyright and added entitys)
Asa Dotzler wrote: > We're getting geared up to do another Firefox update, Firefox 1.0.2, and > to do our first Thunderbird update -- which will also be called 1.0.2, > just to keep things in sync. Those releases are scheduled to happen very > soon, but there are no changes required from the L10N teams.
>> We're getting geared up to do another Firefox update, Firefox 1.0.2, >> and to do our first Thunderbird update -- which will also be called >> 1.0.2, just to keep things in sync. Those releases are scheduled to >> happen very soon, but there are no changes required from the L10N teams.
> We simply need you all to test the Firefox 1.0.2 builds because, like > 1.0.1, we're not allowing any changes in (we did take a change to update > the copyright date). We'll announce here when the Firefox 1.0.2 > localization builds are ready for testing. When you've tested your > build, you'll note that it's ready for shipping in the Firefox 1.0.2 > localization bug <https://bugzilla.mozilla.org/show_bug.cgi?id=286605>.
I am totally beginer to all this CVS stuff. I have just learned to use the CVS account for the eu-ES firefox l10n.
I have corrected the app.update.url string that was pointing to the wrong file ... I've updated the file through the CVS using AVIARY_1_0_20040515_BRANCH files.
i) is that correct? should I write something in any bug?
ii) is it valid for this 1.0.2 release?
iii) When you ask us to test the Firefox 1.0.2 builds, what do you mean? ... just install them and check if the program runs, or is there any protocol to do it?
thank you very much ... I'm sorry for the questions, but I am quite lost!!
We're waiting whether we should include same copyright (and some other) chenges as en-US's one into our localized Thunderbird too or not. We need your decition about this, Asa (or some others who can answer).
I checked our Firefox l10N builds' copyright are fixed by chase (Thanks!). All the more reason to be fixed. We will use same 1.0.2 version number for Firefox and Thunderbird, and we should use same copyright years for both of them.
We already prepared both builds with completely same langpack and builds with langpack including only the same diff as en-US (not including any other fix/change). We now mainly checking later builds since I believe we should fix copyright years. # in the above url, tailing '0.6.10' of filename means same langpack as # 1.0 and '0.6.10.1' means updated langpack
To check both builds at the same time is not efficient and we are happy if you will answer about this soon.
On Fri, 18 Mar 2005 17:31:29 +0200 Ville Pohjanheimo <villepohjanhe...@fastmail.fm> wrote
> >> Please give us a approval to fix only these diff same as en-US one.
> > date: 2005/03/17 01:22:10; author: cmp%mozilla.org; state: Exp; lines: > > +1 -1 > > Land attachment 177670 from bug 278936 to bump the year in the about > > dialog to 2005 for the locales receiving the check-in.
> > This is the german log, Chase did update the copyright notice for all > > locales himself.
> > If your locale has no update to > > browser/locale/ab-CD/chrome/browser/aboutDialog.dtd, yell.
> umm.. dynamis was talking about Thunderbird... the whole message through. > Chase would find it mighty difficul to update Thunderbird locales (other > than en-US) AFAIK.
Yes, I'm talking about Thunderbird. Thanks confirming.
> To reiterate: Is it ok to do the same changes in non en-US Thunderbirds as > has already been made to en-US (changes to copyright and added entitys)
>> We simply need you all to test the Firefox 1.0.2 builds because, like >> 1.0.1, we're not allowing any changes in (we did take a change to >> update the copyright date). We'll announce here when the Firefox 1.0.2 >> localization builds are ready for testing. When you've tested your >> build, you'll note that it's ready for shipping in the Firefox 1.0.2 >> localization bug <https://bugzilla.mozilla.org/show_bug.cgi?id=286605>.
> I am totally beginer to all this CVS stuff. I have just learned to use > the CVS account for the eu-ES firefox l10n.
> I have corrected the app.update.url string that was pointing to the > wrong file ... I've updated the file through the CVS using > AVIARY_1_0_20040515_BRANCH files.
> i) is that correct? should I write something in any bug?
> ii) is it valid for this 1.0.2 release?
> iii) When you ask us to test the Firefox 1.0.2 builds, what do you > mean? ... just install them and check if the program runs, or is there > any protocol to do it?
All that you touch You Change. All that you Change Changes you. The only lasting truth is Change O.Butler ------------------------------------------------------