Fix Japanese L10N for Firefox 2.0.0.1

RESOLVED FIXED

Status

Mozilla Localizations
ja / Japanese
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: dynamis (Tomoya ASAI), Assigned: dynamis (Tomoya ASAI))

Tracking

({verified1.8.1.1})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

11 years ago
ja/ja-JP-mac locale already have some individual bugs for some critical problems and this is the bug including all other less-critical fix for Firefox 2.0.0.1.

I'll attatch a patch and add explanation about the diff.
(Assignee)

Comment 1

11 years ago
Created attachment 246284 [details] [diff] [review]
l10n update patch from 2.0 to 2.0.0.1

This is the patch including diff from 2.0 to 2.0.0.1.
requesting approval1.8.1.1

Detail:
 - credits.dtd#credit.translation:
  * sort names by familiname, not by first name 
  * add names we can get their agreement after the 2.0 string freeze
 - phishing-afterload-warning-message.dtd#safeb.palm.accept.*:
  * the link is not to user's homepage but to searchengine's one and fix it
 - bookmarks.html:
  * change names according to the actual page titles which was decided after 
    string freeze of locale files
 - fix of styles and intl.css
  * To support Windows Vista, which has new defaut font, Meiryo.
    Meiryo font is larger than default font of Win XP and require larger windows.
 - incompatible.warning
  * just fix of typo
Attachment #246284 - Flags: approval1.8.1.1?

Comment 2

11 years ago
Comment on attachment 246284 [details] [diff] [review]
l10n update patch from 2.0 to 2.0.0.1

[ja/ja-JP-mac] approval to fix a bunch of nits and changes to link titles in bookmarks.html for Firefox 2.0.0.1.
Attachment #246284 - Flags: approval1.8.1.1? → approval1.8.1.1+

Comment 3

11 years ago
[mass-verified1.8.1.1 message, filter on this if you need to]

This bug has an approved patch, but not the verified1.8.1.1 keyword.

Please make sure that the approved patch is landed (add the fixed1.8.1.1 keyword then) and tested. If you verified that the bug in question is indeed fixed on the 1.8 branch nightlies, please add the verified1.8.1.1 keyword.

We need to get the QA activities around Firefox 2.0.0.1 up to speed so that we can feel good about releasing this update.
(Assignee)

Updated

11 years ago
Keywords: fixed1.8.1.1
(Assignee)

Comment 4

11 years ago
I verified the fix with latest tinderbox builds.

-> RESOLVED FIXED verified1.8.1.1
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
(Assignee)

Updated

11 years ago
Keywords: fixed1.8.1.1 → verified1.8.1.1
You need to log in before you can comment on or make changes to this bug.