Closed Bug 286605 (fx102l10n) Opened 20 years ago Closed 19 years ago

ship Firefox 1.0.2 l10n builds

Categories

(Firefox :: General, defect)

1.0 Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: chase, Assigned: chase)

Details

Collect and ship all ready l10n builds for Firefox 1.0.2.  Use this bug as a
tracking bug for pending localizations, as well.
Alias: fx102l10n
Status: NEW → ASSIGNED
1. As of March 17, 2004 at 11:24 PDT, we are not code-complete for 1.0.2.
   We'll let you know when we are.

2. Build sign offs in this bug should be of the form:

     <locale> ready for staging

   Example: for cs-CZ:

     cs-CZ ready for staging

   If the locale isn't ready to ship, then note so by saying:

     <locale> not ready for staging

3. Each locale should have sign off on its builds by their locale owner.
(In reply to comment #1)
> 3. Each locale should have sign off on its builds by their locale owner.

Of course I meant:

3. Each locale should have sign off on its builds only by their locale owner.
Hardware: PC → All
sl-SI ready for staging

(tested the build in
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/aviary1.0.1-l10n-candidates/
as linked by Asa in the newsgroup)
If I understand Asa right, then you're ready now, so here is the status for de-DE:

Even though, shipping another version with the bug in the Software-listing of
Windows is acutally inacceptable:

de-DE ready on all OS's for 18-Mar-2005 builds
cs-CZ ready for staging
hu-HU ready for staging
pt-PT ready for staging
Yes, we're ready now.  The builds can be found (as cited in Asa's message and
comment #3) at
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/aviary1.0.1-l10n-candidates/.
ru-RU ready for staging
el-GR ready for staging
fr-FR ready for staging
is anyone actively looking at/responsible for the Dutch version? 
fi-FI ready for staging
es-ES is OK with win32 and linux. I couldn't test Mac.
ro-RO Linux is go.
Will post results for Windows later today.
Won't be able to test on Mac, any help is welcome O:)
ca-AD ready for staging
pt-BR ready for staging
ko-KR ready for staging
Our QA team (Mozilla Korean Project)  tested them.
ro-RO Linux and Windows are ready.
en-GB win32 is go.
Will test with Linux within 24hrs.
I can't test Mac, any help welcome :)
es-AR ready for staging.

Windows and Linux fully tested.
As usual Mac wasn't tested, but should work ok.
ja-JP ready for staging
Each build is checked by plural QA testers and no regression found.

for windows installer, use below modefied build please as is always.
http://ftp.mozilla-japan.org/pub/mozilla-japan/firefox/development/1.0.2/firefox-1.0.2rc.ja-JP.win32.installer.exe
# see bug 266309
eu-ES ready for staging
it-IT is ready for staging
(In reply to comment #12)
> is anyone actively looking at/responsible for the Dutch version? 

If it needs to be asked, that's a good question.  I do not know the answer to
it, however.  Please ask in npm.l10n to get clarification.  Thanks.
zh-TW ready for staging

Ok, I'm not the owner. But seems that the owner of zh-TW locale cannot handle
this now. (I can't get into contact with him for a long time. Last time he reply
my mail is Feb 2nd.)

Mozilla Taiwan Community have tested the RC builds.
(http://forum.moztw.org/viewtopic.php?p=7163)
mk-MK ready for staging
ga-IE ready for staging
tr-TR Firefox 1.0.2 ready for staging.
We have testet, MAC, Linux and windows Versions. 




we would like some changes too. Can anyone approve this patch here,(access.key
and translation corrections)

https://bugzilla.mozilla.org/show_bug.cgi?id=285777

or we must wait to Firefox 1.1 ?

Thanks
erkaN
(In reply to comment #29)
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=285777
> 
> or we must wait to Firefox 1.1 ?

wait for 1.1, please.
(Further to comment #20)
> en-GB win32 is go.
> Will test with Linux within 24hrs.

en-GB linux & win32 ready for staging.
sv-SE ready for staging
(In reply to comment #25)
> (In reply to comment #12)
> > is anyone actively looking at/responsible for the Dutch version? 
> 
> If it needs to be asked, that's a good question.  I do not know the answer to
> it, however.  Please ask in npm.l10n to get clarification.  Thanks.

Posted a message there.

FWIW, if no one is responsible, then i'm willing to sign it off if needs be.
Tested and approve of the Win XP version. Will check Mac OS X and Linux tonight.
I CC'ed the project leader after comment 12 was made. I will CC some other
people as well who might have time to check 1.0.2 nl-NL in time.
(In reply to comment #23)
> eu-ES ready for staging

 I've realized that the app.update.url is still pointing to the en-US.rdf file.
I changed it last day through the CVS:

http://lxr.mozilla.org/l10n-aviarybranch/source/toolkit/locales/eu-ES/chrome/mozapps/update/update.properties#11

 is there anything else I can do to correct it? any help?
nl-NL seems ready for staging as far I can see (Windows+Linux), but I suppose
Tim Maks (the project leader) has to speak the final word. Or is this enough?
(In reply to comment #36)
> nl-NL seems ready for staging as far I can see (Windows+Linux), but I suppose
> Tim Maks (the project leader) has to speak the final word. Or is this enough?

Tim: i've tested the MAC build and that one looks fine too. 

Since i didn't know if anyone can test the norwegian version on Mac, i've done
that as well. 
firefox-1.0.2.nb-NO.mac.dmg has a dead default bookmark for new profiles. The 
Live bookmark currently points to www.nrk.no/rss which is not an rss file
anymore. The correct link should be http://www.nrk.no/nyheiter/siste.rss
(In reply to comment #0)
> Collect and ship all ready l10n builds for Firefox 1.0.2.  Use this bug as a
> tracking bug for pending localizations, as well.

da-DK ready for staging....mac, lin and win.

/Søren Christensen 

For the record:

  * the Firefox 1.0.1 l10n ship bug can be found at bug 283325
  * the Thunderbird 1.0.2 l10n ship bug can be found at bug 286606
pl-PL:
 - Windows is OK
 - Mac is OK
 - Linux tar.gz is OK
 - Linux installer misses master.ini for talkback and fails to work with
talkback. Chase is investigating.
(In reply to comment #40)
>  - Linux installer misses master.ini for talkback and fails to work with
> talkback. Chase is investigating.

This issue was fixed, so we're ready to be released.
I just now fixed the app.update.url problem in cy-GB, pa-IN, and sk-SK, so those
localizations should not ship any build older than tomorrow.
I'd also note that eu-ES should probably fix the "extend=true" in
toolkit/locales/eu-ES/chrome/global/printdialog.properties before shipping.
There is no Bengali/Bangla locale present in 1.0.1. It's very important to have
Bangla language in Language/Fonts section. Some days back I have submitted bn-BD
(Bengali-Bangladesh) CLDR data to Unicode. You can find the information from
http://www.jtcsv.com/cgibin/locale-bugs/?findid=522

Please make some step to add bn-BD locale in FireFox as my team already did
FireFox interface translation
( http://www.ekushey.org/mozilla/firefox.png )

Off Topic: We also need Bengali language in other Mozilla products. So please
tell me what is the procedure to submit the request for other Mozilla products.
(In reply to comment #44)
> Please make some step to add bn-BD locale in FireFox as my team already did
> FireFox interface translation
> ( http://www.ekushey.org/mozilla/firefox.png )
> 
> Off Topic: We also need Bengali language in other Mozilla products. So please
> tell me what is the procedure to submit the request for other Mozilla products.

This is something that should have been posted in the
netscape.public.mozilla.l10n newsgroup, not here.  This bug is for people
actively involved in shipping their locales as part of the Firefox 1.0.2
release, not for requests for new locales.
(In reply to comment #43)
> I'd also note that eu-ES should probably fix the "extend=true" in
> toolkit/locales/eu-ES/chrome/global/printdialog.properties before shipping.

fixed thanks to David ... so now eu-ES is ready for staging
I updated the he-IL builds to include an RTL theme since they don't include one
yet. this was also done in 1.0 and 1.0.1.

i did some testing according to the instructions at:
http://wiki.mozilla.org/MozillaQualityAssurance:l10n_checklist#For_Firefox

and everything seems to be fine. i put the localized files here:

http://www.viewpoints.co.il/firefox/1.0.2/

can you please upload them to mozilla ftp?
(In reply to comment #36)
> nl-NL seems ready for staging as far I can see (Windows+Linux), but I suppose
> Tim Maks (the project leader) has to speak the final word. Or is this enough?
(In reply to comment #37)
Tim: i've tested the MAC build and that one looks fine too. 

Thanks both for testing,

Tim Maks

ps nl-NL is allready staged
And released. Not sure if that should have been possible without you; perhaps
something to look into for the MLP staff?
(In reply to comment #52)
> And released. Not sure if that should have been possible without you; perhaps
> something to look into for the MLP staff?

in this case it was handy (i was away the last  1 1/2 week) but it is not right
indeed.
nb-NO ready for staging
We have released Bangla-Bangladesh Language pack. But what are the process to
add bn-BD officially to FireFox. You can find detail at http://firefox.ekushey.org
(In reply to comment #46)
> 
> fixed thanks to David ... so now eu-ES is ready for staging

is there any chance to get the firefox eu-ES files here?

  http://www.mozilla.org/products/firefox/all.html

... anything we can do?
(In reply to comment #47)
> I updated the he-IL builds to include an RTL theme since they don't include one
> yet. this was also done in 1.0 and 1.0.1.
> ...
> and everything seems to be fine. i put the localized files here:
> 
> http://www.viewpoints.co.il/firefox/1.0.2/

Will a Mac version be available soon?
(In reply to comment #55)
> We have released Bangla-Bangladesh Language pack. But what are the process to
> add bn-BD officially to FireFox. You can find detail at http://firefox.ekushey.org

Sorry, we're not taking new locales for the 1.0.x branch anymore. Please prepare 
to get into 1.1, some documentation on that is on 
http://www.mozilla.org/projects/l10n/registration.html and 
http://wiki.mozilla.org/L10n:Firefox_Extras
I tested Linux installer builds from latest-aviary1.0.1-l10n/ dated from
30-March-2005.

the following passed:

* cy-GB - pass
* eu-ES - pass
* pa-IN - pass, but rather cursory, since my machine lacks Punjabi fonts

...and the other locales:

* sk-SK - fail, Help > About results in XML error (but other tests fine)
* sq-AL - fail, still has the empty bookmark toolbar folder and blank bookmark
about live-bookmarks.html 
zh-CN ready for staging...
Sorry I'm late..
zh-CN ready for staging...
I tested Mac OS X builds from latest-aviary1.0.1-l10n/ dated from
29-March-2005, and the results are the same as for Linux (comment 59):

the following passed:

* cy-GB - pass
* eu-ES - pass
* pa-IN - pass, but rather cursory, since my machine lacks Punjabi fonts

...and the other locales:

* sk-SK - fail, Help > About results in XML error (but other tests fine)
* sq-AL - fail, still has the empty bookmark toolbar folder and blank bookmark
about live-bookmarks.html 
tested with 3/31 builds from latest-aviary1.0.1-l10n/ on Windows XP sp2.

these locales passed:

* cy-GB
* eu-ES
* pa-IN

but, as with the Mac and Linux builds, these locales failed:

* sk-SK - Help > About results in XML error
* sq-AL - still has the empty bookmark toolbar folder and blank bookmark about
live-bookmarks.html
Using the build in the 20050414 build for sq-AL, I don't see the two issues that
Sarah noted in the earlier build. The sq-AL build passes on the Mac.

(In reply to comment #62)
> I tested Mac OS X builds from latest-aviary1.0.1-l10n/ dated from
> 29-March-2005, and the results are the same as for Linux (comment 59):
> 
> the following passed:
> 
> * cy-GB - pass
> * eu-ES - pass
> * pa-IN - pass, but rather cursory, since my machine lacks Punjabi fonts
> 
> ...and the other locales:
> 
> * sk-SK - fail, Help > About results in XML error (but other tests fine)
> * sq-AL - fail, still has the empty bookmark toolbar folder and blank bookmark
> about live-bookmarks.html 
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.