Closed Bug 1005107 Opened 11 years ago Closed 11 years ago

charsetMenu.properties not included in localized files

Categories

(Firefox for Android Graveyard :: Locale switching and selection, defect)

ARM
Android
defect
Not set
normal

Tracking

(firefox30 fixed, firefox31 fixed, firefox32 fixed, b2g-v1.4 fixed, fennec30+)

VERIFIED FIXED
Firefox 32
Tracking Status
firefox30 --- fixed
firefox31 --- fixed
firefox32 --- fixed
b2g-v1.4 --- fixed
fennec 30+ ---

People

(Reporter: Margaret, Assigned: Margaret)

References

Details

Attachments

(2 files)

With bug 943262, we started using toolkit's CharsetMenu.jsm for the character encoding menu, and that pull strings from charsetMenu.properties. It appears that this file is not being localized on Fennec. Bigger question: Why do the en-US strings work? If we want to avoid accidentally making mistakes like this, I think that something should break during the development process.
tracking-fennec: --- → ?
Cc'ing Pike, since this is related to bug 792077.
Assignee: nobody → margaret.leibovic
tracking-fennec: ? → 30+
I haven't made a multi-locale build to test this, but I just copied what we do for other toolkit files.
Attachment #8422289 - Flags: review?(l10n)
Comment on attachment 8422289 [details] [diff] [review] Include charsetMenu.properties in localized files Review of attachment 8422289 [details] [diff] [review]: ----------------------------------------------------------------- Yep, this looks right.
Attachment #8422289 - Flags: review?(l10n) → review+
Comment on attachment 8422289 [details] [diff] [review] Include charsetMenu.properties in localized files [Approval Request Comment] Bug caused by (feature/regressing bug #): bug 943262 User impact if declined: character encoding menu won't be localized Testing completed (on m-c, etc.): just landed on fx-team Risk to taking this patch (and alternatives if risky): adds a new toolkit locale file to our multi-locale build process String or IDL/UUID changes made by this patch: adds new file to multi-locale build, but this file will already exist in desktop locales Maybe Pike or flod can chime in about the l10n impact uplifting this would have, but AIUI this shouldn't cause a problem.
Attachment #8422289 - Flags: approval-mozilla-beta?
Attachment #8422289 - Flags: approval-mozilla-aurora?
From l10n point of view this change is welcome on aurora and beta: no new strings required, and we localize part of the UI. Just need to verify that everything works as expected on trunk.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 32
(In reply to Francesco Lodolo [:flod] from comment #6) > Just need to verify that everything works as expected on trunk. Let me know when we can uplift this patch to aurora & beta. Thanks
Flags: needinfo?(francesco.lodolo)
Attached image Nexus 7 screenshot
Menu is correctly localized in today's build.
Flags: needinfo?(francesco.lodolo)
Status: RESOLVED → VERIFIED
Attachment #8422289 - Flags: approval-mozilla-beta?
Attachment #8422289 - Flags: approval-mozilla-beta+
Attachment #8422289 - Flags: approval-mozilla-aurora?
Attachment #8422289 - Flags: approval-mozilla-aurora+
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: