Closed Bug 283325 (101l10n) Opened 20 years ago Closed 20 years ago

ship Firefox 1.0.1 l10n builds

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Version:
1.0 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: chase, Assigned: chase)

Details

Collect and ship all ready l10n builds for Firefox 1.0.1. Use this bug as a tracking bug for pending localizations, as well.
Status: NEW → ASSIGNED
Who should report that build is ready? MLP? Pike+Me? Team owner/peer?
Locales that didn't have a 1.0 release will be reported by issuing their QA sign-off request into Bugzilla. For the record, which locales are about to enter that phase? If there are any bugs open for these, could you post their bug numbers here? Locales that did have a 1.0 release would probably be best to have their team owner sign-off on them just as a doublecheck that everything's in place. If we don't get sign-off, though, I think we're reasonably confident they're of the same quality as what went in 1.0. We'll do a quick review on our end to sanity check before posting them. Any help you and/or Pike could give us there would be greatly appreciated.
Alias: 101l10n
List of l10ns that were not released for 1.0 and we can get them for 1.0.1: cy-GB ga-IE pt-PT (bug 282727. I did not check that in because Axel wrote he's not happy with the situation around. Not sure what's going on) sk-SK sq-AL mk-MK lt-LT (blocked by bug 281662) eu-ES km-KH (no Windows installer and no last review - bug 267909) pa-IN af-ZA ar-JO (no response after review - bug 278651) Those are locales that are on my radar.
Note that we don't seem to have start page snippets for any of the new locales, I think we forgot to communicate that they need to be translated.
(In reply to comment #4) > Note that we don't seem to have start page snippets for any of the new > locales, I think we forgot to communicate that they need to be translated. I'm quite sure that I sent mk-MK snippets to MLP staff. If they got lost or something I can send them again.
(In reply to comment #5) > (In reply to comment #4) > > Note that we don't seem to have start page snippets for any of the new > > locales, I think we forgot to communicate that they need to be translated. > > I'm quite sure that I sent mk-MK snippets to MLP staff. If they got lost or > something I can send them again. I'm not seeing neither mk-MK snippets nor other snippets in my pending or archived mlp-staff mails, so either they disappeared (got deleted, whatever) or weren't sent there.
lt-LT, pt-PT are checked in. kh-KH and ar-JO will not get in because of lack of response from owners, rest should go for 1.0.1.
el-GR ready for staging.
Flags: certification-l10n?
hu-HU ready for staging
it-IT ready for staging
Flags: certification-l10n? → certification-l10n+
nl-NL linux is ready nl-NL windows not because of bug 280084
ro-RO windows and linux are ready. If a Mac owner could have a quick look at ro-RO Mac, I'll be forever grateful ;-)
sq-AL didn't have an official 1.0 release, because of https://bugzilla.mozilla.org/show_bug.cgi?id=268717#c8, but I've asked for sign-off anyway, as the issue with that is an empty folder on bookmarks at the Mac buid...
Flags: certification-l10n+ → certification-l10n?
Flags: certification-l10n?
Linux, Windows fi-FI ready for staging Mac should be tested. If anyone else could, we'd appreciate it.
es-AR ready to launch.
ru-RU ready for staging
fr-FR ready for staging Thanks everyone involved
ca-AD is ready for staging. Great work!
de-DE is ready.
pl-PL builds don't have the changes from bug 283235 (which were checked in on Feb 23rd) and it would be really nice if patch for bug 283384 was checked in (releaseURL is wrong). Apart from these minor issues pl-PL builds are OK on Mac, Linux and Windows.
cs-CS should be ready for staging windows - 2 testers of 4 experienced the crash as in bug 280084 mac - nobody tested
I did some basic smoketests on the mac builds of ro-RO and fi-FI. (those in latest-l10n) Both are fine. So as the respective l10n-owners already signed off the rest, I would suggest: ro-RO Mac } fi-FI Mac } ready to stage
pl-PL Linux and Windows are ready (Feb 24th builds from latest-aviary1.0.1-l10n). Mac version _should_ be OK when the Feb 24th build is out (if it has the right RSS for 7thGuard.net in liveboomarks - it is). We decided to accept these even though bug 283384 isn't fixed.
ko-KR is ready. Thanks..
af-ZA is ready for staging.
en-GB ready for staging
nb-NO ready for staging.
sl-SI ready for staging
nl-NL ready for staging
sv-SE ready for staging
tr-TR ready for staging.
es-ES issues: - Linux: OK - Win32: If you choose to install talkback, installation throws an error that can't find talkback. No option to go on, but closing the window lets go on, but talkback doesn't work. - Mac: no chance to try.
es-ES issues: - Linux: OK - Win32: If you choose to install talkback, installation throws an error that can't find talkback. No option to go on, but closing the window lets go on, but talkback doesn't work. This doesn't happen in 1.0. - Mac: no chance to try.
Last try for es-ES in the deuce directory fixes the talkback problem. Still not able to try mac, but at least linux and win32 installers are ok for me.
I've tested some of the 1.0.1 locales (grabbed from aviary1.0.1-l10n-candidates-deuce). some of these need another bug spun off for the issues noted. I'm currently downloading the remaining Mac and Linux builds from aviary1.0.1-l10n-candidates-deuce --once I've got the results from those I'll post here. ca-AD: overall Pass, but the Mac build but has a Linux oriented bookmark (trivial, shouldn't block release). de-DE: Pass. el-GR: Pass. es-AR: Asa noticed that they have Google and Yahoo in the correct order but then at the bottom of the list they have "Google (US)" and "Yahoo (US)" As he understood it, they're not supposed to alter the primary Google and Yahoo plugins and I'm assuming they have if they've added these two to the end of the list. fi-FI: Pass. fr-FR: Pass. hu-HU: Overall pass, but there are bookmarks (in the 2nd and 3rd folders) which are unlabeled that goes to the hungarian version of google.com and mozillazine, respectively. it-IT: Pass. nl-NL: Overall pass, but 3rd BM folder contains a bm whose label has an unescaped entity. pl-PL: Fail (or, for cbeard and rebron to review), since Yahoo is missing in the search toolbar. ro-RO: Pass. ru-RU: Fail (or, for cbeard and rebron to review), since Yahoo is missing in the search toolbar. sq-AL: Fail, still problems with bookmarks and the initial size of the Preferences dialog --see bug 283378 comment 8.
Hardware: PC → All
(In reply to comment #35) > pl-PL: Fail (or, for cbeard and rebron to review), since Yahoo is missing in the > search toolbar. > ru-RU: Fail (or, for cbeard and rebron to review), since Yahoo is missing in the > search toolbar. Yahoo is missing in pl-PL because there's no Polish version of this site. Same thing with ru-RU. Should we add a link to the US Yahoo? This doesn't make much sense...
...and the remaining locales, downloaded from aviary1.0.1-l10n-candidates-deuce --again, if the owners of locales with issues noted below could spin off separate bugs for the problems, we would really appreciate it! (note that some wouldn't necessarily be ship blockers.) af-ZA: Pass. ast-ES: Overall pass, but the start page isn't localized. cs-CZ: Fail (or, for cbeard and rebron to review), since Yahoo is missing from the search toolbar. cy-GB: Pass. da-DK: Overall pass, but the start page isn't localized. en-GB: Pass. es-ES: Pass. eu-ES: Pass. ga-IE: Pass. he-IL: Pass. ja-JP / ja-JPM: Pass. ko-KR: Pass. mk-MK: No Windows build available at time of testing, but Linux and Mac pass. nb-NO: Overall pass, but the start page isn't localized. pa-IN: Fail, XUL error on startup. pt-BR: Pass. pt-PT: Pass. sk-SK: * Fail, because the About dialog displays only a XUL error (Pomocnik > O programe Mozilla Firefox). * also, on Mac the toolbar bookmarks overlap oddly with each other --but this might be my machine not having the right fonts. sl-SI: Fail (or, for cbeard and rebron to review), since Yahoo is missing from the search toolbar. sv-SE: Pass. tr-TR: Overall pass, but the start page isn't localized. zh-CN: * Fail (or, for cbeard and rebron to review), since Yahoo is missing from the search toolbar. * a bunch of the bookmarks in the 2nd folder still reference Firebird: some of these redirect to Firefox pages, but some result fail in 404 errors. * on Mac, a couple of the toolbar bookmarks are linux-oriented. zh-TW: Fail (or, for cbeard and rebron to review), since Yahoo is missing from the search toolbar.
sl-SI has been approved in 1.0 to ship the search plugins that it does (ie, no Yahoo!). See bug 265249. Does it need a second approval?
(In reply to comment #37) > cs-CZ: Fail (or, for cbeard and rebron to review), since Yahoo is missing > from the search toolbar. Search engines in cs-CZ localization are okay, they were approved by Rafael Ebron in bug 265160 (comment #6 from 2004-11-08). Who could push cs-CZ build into release?
da-DK ready for staging...
(In reply to comment #37) > tr-TR: Overall pass, but the start page isn't localized. We have translated all DTD- and properties files. I can chekup again. Can you say to me please, which file(s) do you mean with startpage? Thanks erkaN
(In reply to comment #41) > I can chekup again. > Can you say to me please, which file(s) do you mean with startpage? hi erkaN, the default homepage (aka, startpage) is actually server-controlled, so I don't think there's anything firefox localizers need to do (ie, it wouldn't block 1.0.1 build shipping). cc'ing Luke: Luke, in comment 35 and comment 37 there are a few locales whose startpage is completely in english. is there anything on your end you could do there?
(In reply to comment #35) > ru-RU: Fail (or, for cbeard and rebron to review), since Yahoo is missing in the > search toolbar. > Search engines in ru-RU localization are okay, they were approved by Rafael Ebron in bug 265882 (comment #9).
Re comment 41: The extra bits that have to be translated for the start page are described in http://wiki.mozilla.org/wiki/L10n:Firefox_Extras under "Start Pages"
I added a blurb about the start page snippets to the Wiki, please make sure to localize the snippets for your locale, in addition to the start pages. See http://wiki.mozilla.org/wiki/L10n:Firefox_Extras#Start_Page_Snippets and http://wiki.mozilla.org/wiki/L10n:Firefox_Extras#Start_Pages.
(In reply to comment #42) > (In reply to comment #41) > > I can chekup again. > > Can you say to me please, which file(s) do you mean with startpage? > > hi erkaN, the default homepage (aka, startpage) is actually server-controlled, > so I don't think there's anything firefox localizers need to do (ie, it wouldn't > block 1.0.1 build shipping). Hi sairuh, We have translated following Startpages long ago. http://www.mozilla-europe.org/tr/products/firefox/start/central.html http://www.mozilla-europe.org/tr/products/firefox/start/get-involved.html http://www.mozilla-europe.org/tr/products/firefox/start/about.html Thanks for shipping erkaN
In the future, if there are no changes to the search plug-ins in terms of additions/subtractions from one minor version to the next, i.e. Firefox 1.0 to Firefox 1.0.1 then we're ok. For major releases, e.g. Firefox 1.0 to 1.1 we can revisit the search plug-in information. So again, if search plug-ins, order, any code in regards to search plug-ins didn't change in 1.0.1 (or in other words was approved in Firefox 1.0), then we're all approved for Firefox 1.0.1.
Sarah: in pl-PL case, take a look at bug 265231. We are allowed to use this list of searchplugins and bookmarks.
per rafael's comment 47, the search plugin stuff is fine if they are the same as the ffox 1.0 version. and per bug 265231, bug 265882, bug 265160 and bug 265249 those locales are good to go for 1.0.1.
pt-BR ready for staging.
(In reply to comment #37) >zh-CN: >* Fail (or, for cbeard and rebron to review), since Yahoo is missing from the >search toolbar. Search engines for zh-CN is approved in bug#266021.
I don't understand why they were shipped if they did not pass QA!
i updated the he-IL builds, to include an rtl theme, since the orignals don't include an rtl theme. this was also approved in firefox 1.0. the builds are currently located at: http://www.viewpoints.co.il/firefox/1.0.1/ the build for mac is not yet ready, and we hope to finish it soon. can you please add them to http://www.mozilla.org/products/firefox/all.html?
Bsmedberg discovered this, es-ES points to the wrong update file (https\://update.mozilla.org/update/firefox/en-US.rdf). es-ES users will get 1.0.1 en-US. In any case we need to fix this for 1.0.1. So: es-ES: * Fail until http://lxr.mozilla.org/l10n-aviarybranch/source/toolkit/locales/es-ES/chrome/mozapps/update/update.properties#43 is fixed.
Other locales that point to the en-US.rdf: sk-SK, cy-GB, eu-ES and pa-IN. I've commented in the cy-GB release bug, didn't find release bugs for the others.
(In reply to comment #37) > zh-TW: Fail (or, for cbeard and rebron to review), since Yahoo is missing from > the search toolbar. Due to bug 266042, we (zh-TW l10n team) have to remove yahoo from search toolbar. So I think zh-TW build could be labeled "PASS". :)
right, I spoke with Rafael and he said that the Yahoo search plugin wasn't in zh-CN and zh-TW for ffox 1.0, so it's okay for ffox 1.0.1 as well. :)
(In reply to comment #56) > Other locales that point to the en-US.rdf: sk-SK, cy-GB, eu-ES and pa-IN. I've > commented in the cy-GB release bug, didn't find release bugs for the others. These builds won't ship until this is fixed. Any other build that has this problem will be pulled and won't be shipped until it is fixed. Thanks for finding this Peter.
(In reply to comment #55) > Bsmedberg discovered this, es-ES points to the wrong update file > (https\://update.mozilla.org/update/firefox/en-US.rdf). es-ES users will get > 1.0.1 en-US. In any case we need to fix this for 1.0.1. So: This is already solved in bug 284489
sq-AL was removed. Will ship after the issues with the locale are sorted. The following locales are now live for 1.0.1 on the FTP site and website: * af-ZA * ast-ES * ca-AD * cs-CZ * da-DK * de-DE * el-GR * en-GB * en-US * es-AR * fi-FI * fr-FR * ga-IE * he-IL * hu-HU * it-IT * ko-KR * nb-NO * nl-NL * pl-PL * pt-BR * pt-PT * ro-RO * ru-RU * sl-SI * sv-SE * tr-TR * zh-CN * zh-TW
es-ES has been made live using a build from latest-aviary1.0.1-l10n. We are still waiting on a mac build, too. When it's complete, I'll add it to the release directory.
(In reply to comment #63) > The following mirror still has 14 locales: > http://64.12.168.243/pub/mozilla.org/firefox/releases/1.0.1/win32/ Myk, that's one of the AOL boxes. Who do we contact for them?
The following mirror is also not up to date: http://mozilla.mirrors.hoobly.com/firefox/releases/1.0.1/win32/af-ZA/Firefox%20Setup%201.0.1.exe Is there some system for testing all the mirrors? What is the correct way to address this?
Hi, for pa-IN, i update file at https://bugzilla.mozilla.org/show_bug.cgi?id=264621 can some pls check that
ja-JP Firefox 1.0.1 released
I'm afraid dynamis jumped the gun here. When he commented, ja-JP/ja-JPM wasn't fully released. They are both now, though, and the locale files have been tagged.
I wrote above comment just after I found our build on ftp.mozilla.org server. I hasted to make release in time and I was a little confused about precedure to release. I'm sorry and really appreciate Chase's great help.
Resolving fixed. We're done shipping Firefox 1.0.1 builds. See bug 286605 for the Firefox 1.0.2 l10n ship tracker.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
(In reply to comment #59) > (In reply to comment #56) > > Other locales that point to the en-US.rdf: sk-SK, cy-GB, eu-ES and pa-IN. I've > > commented in the cy-GB release bug, didn't find release bugs for the others. > > These builds won't ship until this is fixed. Any other build that has this > problem will be pulled and won't be shipped until it is fixed. Thanks for > finding this Peter. for pa-IN, i updated the file to pa-IN.rdf file at following link https://bugzilla.mozilla.org/show_bug.cgi?id=264621 i think i forget to update infor here
You need to log in before you can comment on or make changes to this bug.