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 220.127.116.11. I'll attatch a patch and add explanation about the diff.
Created attachment 246284 [details] [diff] [review] l10n update patch from 2.0 to 18.104.22.168 This is the patch including diff from 2.0 to 22.214.171.124. requesting approval126.96.36.199 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: approval188.8.131.52?
Comment on attachment 246284 [details] [diff] [review] l10n update patch from 2.0 to 184.108.40.206 [ja/ja-JP-mac] approval to fix a bunch of nits and changes to link titles in bookmarks.html for Firefox 220.127.116.11.
Attachment #246284 - Flags: approval18.104.22.168? → approval22.214.171.124+
[mass-verified126.96.36.199 message, filter on this if you need to] This bug has an approved patch, but not the verified188.8.131.52 keyword. Please make sure that the approved patch is landed (add the fixed184.108.40.206 keyword then) and tested. If you verified that the bug in question is indeed fixed on the 1.8 branch nightlies, please add the verified220.127.116.11 keyword. We need to get the QA activities around Firefox 18.104.22.168 up to speed so that we can feel good about releasing this update.
I verified the fix with latest tinderbox builds. -> RESOLVED FIXED verified22.214.171.124
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.