Closed
Bug 352109
(fx20-be)
Opened 18 years ago
Closed 18 years ago
[be] Ship Firefox 2
Categories
(Mozilla Localizations :: Other, defect)
Mozilla Localizations
Other
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.8final
People
(Reporter: Pike, Assigned: mozilla_by)
References
Details
Attachments
(1 file)
49.33 KB,
image/jpeg
|
Details |
Reporter | ||
Updated•18 years ago
|
Alias: fx20-be
Target Milestone: --- → mozilla1.8final
Comment 1•18 years ago
|
||
is be ready for RC1? any outstanding issues still to work on?
Reporter | ||
Comment 2•18 years ago
|
||
Siarhei, is Byelorussian ready to be released?
There were a few testruns reported on litmus, though I'm not sure Carsten speaks Byelorussian. CCing him to fill in with the details.
If testing shows no blockers, close this bug to indicate sign-off, please. Deadline for sign-off is today, as announced in .l10n.
Comment 3•18 years ago
|
||
(In reply to comment #2)
> There were a few testruns reported on litmus, though I'm not sure Carsten
> speaks Byelorussian. CCing him to fill in with the details.
>
Pike, i will take this and will run a Litmus Smoketest with this be-Build. The last Test from QA was during RC1.
Reporter | ||
Comment 4•18 years ago
|
||
Thanks. We still need some QA reporting with language skills independent of that, of course.
Comment 5•18 years ago
|
||
Okay, smoketest and l10n Test was run, also looked for trademark issues:
Build: Mozilla/5.0 (Windows; U; Windows NT 5.0; be; rv:1.8.1) Gecko/20061010 Firefox/2.0
2 Things. In the first Option window in the last sentence of the Systemdefault Settings is half cut, will attach a screenshot.
Also there is Problem with the Helpfile.
1. Its a mix of english and localised, seems only Firefox and the term Options are translated. Example: Check this option if you want Файэфокс to actively check whether
2. The Helpfile is either old or wrong. According to the Helpfile must be a Tab under Options -> Advanced -> Anti-Phishing tab and 3 different options:
Check to see if the site I'm visiting might be a scam
Using a locally stored list
By asking
This is not the case in Firefox 2..there is still no Anti- Phishing Tab
Comment 6•18 years ago
|
||
Reporter | ||
Comment 7•18 years ago
|
||
Carsten, thanks for testing. I wouldn't block on either issue, the pref is still readable, AFAICT, and the help update can come in a later bug. Siarhei, mind filing those and putting me on CC?
(In reply to comment #7)
> Carsten, thanks for testing. I wouldn't block on either issue, the pref is
> still readable, AFAICT, and the help update can come in a later bug. Siarhei,
> mind filing those and putting me on CC?
>
Unfortunately I can't perform testing now. I don't have access to any computer where I could install FF. (In fact, I don't have access for the last month). So, I can't report that the localization is ready to release.
I would have possibility to test the localization next week.
But it is too late.
Bad luck.
Comment 9•18 years ago
|
||
Well, I'm now instructing my Belarusian-speaking friend on how to use litmus, so in fact we'll probably have some Litmus results for Belarusian even today. ;-)
Stay tuned.
Comment 10•18 years ago
|
||
OK, Maciek Krol (http://macie3k.info) submitted all L10n litmus test results, the only issue he found is the Sys Defs groupbox problem mentioned above.
The overall quality of the localization is quite good, he says, and it's OK for us to release it. :)
A link to the results:
http://litmus.mozilla.org/advanced_search.cgi?branch=2.0+Branch&locale=be-BY&platform=Windows&product=Firefox&result_status=&testcase_id=&test_group=Localization+%28l10n%29&start_date=&end_date=&search_field1=&match_criteria1=contains_all&search_value1=&search_field2=&match_criteria2=contains_all&search_value2=&search_field3=&match_criteria3=contains_all&search_value3=&search_field4=&match_criteria4=contains_all&search_value4=&sort_field1=&sort_order1=ASC&sort_field2=&sort_order2=ASC&sort_field3=&sort_order3=ASC&sort_field4=&sort_order4=ASC&limit=15
I suppose we may resolve this bug as fixed, on behalf of Siarhei. Pike? :)
Reporter | ||
Comment 11•18 years ago
|
||
Siarhei, thanks to Maciek we got some testing of your work by someone with language skills, and I'd be fine to take his word for the testing part.
But in the end, you're the owner, and you need to be comfortable with shipping the Byelorussian localization as it is. If so, please resolve the bug fixed to indicate your sign-off.
(Byelorussian or Belarusian? wikipedia says Belorusian, I took the name from the wiki)
Assignee | ||
Comment 12•18 years ago
|
||
The right name is Belarusian.
Thanks to all for your participation.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 13•18 years ago
|
||
Belarusian has missed the 2.0.0.1 train, sadly, I didn't hook this bug up to the right dependencies. Because it was FIXED, though we didn't actually ship 2.0.
Reopening and adding the fixes bug 358065 to the deps here.
Sorry for that. I hooked this up to 2.0.0.2, it's really too late for .1 now.
Assignee | ||
Comment 14•18 years ago
|
||
The locale is ready to be released.
I hope it would be released with 2.0.0.2.
Comment 15•18 years ago
|
||
I'm resolving this as fixed, since Belarusian got released with 2.0.0.4.
Status: REOPENED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•