Bug 352116 (fx20-he)

[he] Ship Firefox 2

RESOLVED FIXED

Status

Mozilla Localizations
he / Hebrew
RESOLVED FIXED
12 years ago
11 years ago

People

(Reporter: Pike, Assigned: tomer)

Tracking

({fixed1.8.1.1})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [Fx 2.0.0.1] QA in process)

Attachments

(3 attachments, 1 obsolete attachment)

(Reporter)

Description

12 years ago
Looking at http://people.mozilla.com/~axel/status-1.8/ and http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-he, the hebrew localisation is behind quite a bit.
Help is broken too, as has been reported in bug 344312.

I'm not setting a milestone on this, waiting for input from the l10n team here.
(Reporter)

Updated

12 years ago
Alias: fx20-he
(Assignee)

Comment 1

12 years ago
I am the person to blame. I need time to finish the project toward 2.0 and CVS access (bug 343315). 

Please assign to me and make it depend on bug 343315.
(Reporter)

Comment 2

12 years ago
Reassigning to Tomer.

I boosted your privs, too, so that you can grab bugs now.
Assignee: tsahi_75 → tomer

Updated

12 years ago
Depends on: 350611

Updated

12 years ago
Depends on: 350594
(Reporter)

Updated

12 years ago
No longer depends on: 350594
(Assignee)

Updated

12 years ago
Blocks: 352499

Updated

12 years ago
Whiteboard: still some work to do. [2 days?]
(Assignee)

Comment 3

12 years ago
After a terrible software crash which lead to data loss, the translation process is back on track. I have to complete the toolkit component translation, and migrate the browser help from version 1.5. 

Estimated completion time: 24 hours.  
Status: NEW → ASSIGNED
(Reporter)

Comment 4

12 years ago
Please don't check into the MOZILLA_1_8_BRANCH without explicit approval, it's closed. Just to make sure you understand that this affects all locales as of now.
(Assignee)

Comment 5

12 years ago
Who can manually approve it? I can email the locale to a driver or attach it here. 
(Reporter)

Comment 6

12 years ago
I guess I'll just do a verbal approval without a patch. Just poke me when you're ready, and I'll sign it off when we have an engineering window.
(Assignee)

Comment 7

12 years ago
I have completed the language pack, hope there is no mistakes in there. The help file still outdated in we are working to complete it in the next day. Should I attach here the file? 
(Assignee)

Comment 8

12 years ago
Created attachment 239930 [details]
he translation for Firefox 2.0

He translation for Firefox 2.0. 

This file is work in progrss:
1. Localized search engines missing. See bug 348114 - We have two engines ready, but wish to get another one or two for inclusion (Waiting for site approvals). 
2. Help not updated. We are working toward finishing it in a day or so. Must of the job (prefs.xhtml) done.
(Assignee)

Updated

11 years ago
Depends on: 356464
(Reporter)

Comment 9

11 years ago
Moving over to 2.0.0.1.
Blocks: 357246
No longer blocks: 350031
Whiteboard: still some work to do. [2 days?] → [Fx 2.0.0.1] still some work to do. [2 days?]
(Assignee)

Comment 10

11 years ago
Can we commit the translation to the CVS? It is quite strange that we have 3.0a1 but no 2.0. 
(Reporter)

Comment 11

11 years ago
Now is the time for landing big changes towards Firefox 2.0.0.1.

a=me for the initial landing, please file follow-up bugs and attach patches on remaining issues coming up.
(Reporter)

Comment 12

11 years ago
Apart from the search engines, I see english descriptions in bookmarks.html still. Could you fix those?

How does the rest of the Hebrew build look, is the testing progressing nicely?
(Assignee)

Comment 13

11 years ago
(In reply to comment #12)
> Apart from the search engines, I see english descriptions in bookmarks.html
> still. Could you fix those?
The translated bookmarks.html has few problems and replaced with the 1.5 version. I'm currently doing the bug hunting, and will have a working bookmarks.html in few hours. Also, the file has "BOOKMARKS TOOLBAR FOLDERr" (Caps are the translated string; note of the postfix "r" with has nothing to do here. 

 
> How does the rest of the Hebrew build look, is the testing progressing nicely?
The Translation is on track, and apart of few problems (The check for updates hangs with XUL error, the tree in the Help is not RTL) we are just fine for shipping. 

I'll attach fixes in the upcoming hours; CVS upload by our working-CVS-account peer will be possible only in about a day due to Sabbath.

Tomer: isn't the help tree issue basically bug 140759?
(Assignee)

Comment 15

11 years ago
(In reply to comment #14)
> Tomer: isn't the help tree issue basically bug 140759?
> 

It is. 

Comment 16

11 years ago
Created attachment 245356 [details] [diff] [review]
[fixed] some fixes to the he translation

fixes for the translation. including the searchplugins and the bookmarks.
Attachment #245356 - Flags: approval-l10n?
(Reporter)

Comment 17

11 years ago
Comment on attachment 245356 [details] [diff] [review]
[fixed] some fixes to the he translation

[he] approval to land additional fixes to make hebrew ready for release.

We still need Mic on the plugins themselves in the search engines bug, I'll look at the technicalities of the plugins once this patch landed.
Attachment #245356 - Flags: approval-l10n? → approval-l10n+

Updated

11 years ago
Attachment #245356 - Attachment description: some fixes to the he translation → [fixed] some fixes to the he translation

Comment 18

11 years ago
Created attachment 245788 [details] [diff] [review]
additional fixes to the he translation

additional fixes for the translation. we hope to get the rest of the help section translated before 2.0.0.1/
Attachment #245788 - Flags: approval-l10n?
(Assignee)

Comment 19

11 years ago
(In reply to comment #18)
> additional fixes for the translation. we hope to get the rest of the help
> section translated before 2.0.0.1/
Reuven, didn't I sent you the updated help section for 2.0?

(Assignee)

Comment 20

11 years ago
Axel: Will Hebrew be released with the other locales for the upcoming 2.0.0.1? 

Comment 21

11 years ago
Created attachment 246151 [details] [diff] [review]
he translation update

this is the help translation from Tomer, and some access keys fixes.
Attachment #246151 - Flags: approval-l10n?

Updated

11 years ago
Attachment #245788 - Attachment is obsolete: true
Attachment #245788 - Flags: approval-l10n?
(Reporter)

Comment 22

11 years ago
Comment on attachment 246151 [details] [diff] [review]
he translation update

[he] approval for landing a bunch of fixes for Hebrew, including a huge chunk for help.

tomer, did you try that code with my testing extension at http://people.mozilla.com/~axel/l10n/?

Regarding shipping, there still seems to be a whole slew of QA work going on, might be a good idea to do some litmus based testing, too.
In the end, we'll need you to "be done" with it, I can't make a call on that from looking at the patches.
(Reporter)

Comment 23

11 years ago
Comment on attachment 246151 [details] [diff] [review]
he translation update

[he] approval for landing a bunch of fixes for Hebrew, including a huge chunk
for help.

Moving approval flag over from approval-l10n to the 1.8.1.1 one, which is the one we use for this release.
Attachment #246151 - Flags: approval-l10n? → approval1.8.1.1+
(Assignee)

Updated

11 years ago
Depends on: 361393
(Reporter)

Comment 24

11 years ago
Adjusting whiteboard to "QA in progress", which I think is more up-to-date.
Whiteboard: [Fx 2.0.0.1] still some work to do. [2 days?] → [Fx 2.0.0.1] QA in process
Keywords: fixed1.8.1.1
Even though attachment 246151 [details] [diff] [review] has landed, it seems there is more needed for full 1.8.1.1 support.
Keywords: fixed1.8.1.1
(Reporter)

Comment 26

11 years ago
Clarification: I will do some further tests, and there will likely be some additional external QA effort next week to check that.

Updated

11 years ago
Keywords: fixed1.8.1.1
Ping: looks like we're shipping he 2.0.0.4 - can this and the tracker it blocks be closed now?
(Assignee)

Updated

11 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.