Closed Bug 439398 Opened 11 years ago Closed 11 years ago
[uk] "Show image" and "view image" should be translated differently
In browser/chrome/browser/browser.dtd there are two labels with very similar text: <!ENTITY showImageCmd.label "Show Image"> <!ENTITY viewImageCmd.label "View Image"> The meaning is different: "Show Image" appears in the context menu for images that were not fully loaded, and will attempt to reload the image. "View image" loads the image stand-alone. The translation of the two texts should be different
Status: NEW → ASSIGNED
Summary: %(uk) "Show image" and "view image" should be translated differently → [uk] "Show image" and "view image" should be translated differently
Comment on attachment 327396 [details] [diff] [review] differentiate those and few related strings a=me, please land this ASAP with a comment referencing this bug and my approval. Use the fixed22.214.171.124 and verified126.96.36.199 keywords to track landing and testing.
Attachment #327396 - Flags: approval188.8.131.52? → approval184.108.40.206+
Checking in browser/chrome/browser/browser.dtd; /l10n/l10n/uk/browser/chrome/browser/browser.dtd,v <-- browser.dtd new revision: 1.30; previous revision: 1.29 done Checking in browser/chrome/browser/setDesktopBackground.dtd; /l10n/l10n/uk/browser/chrome/browser/setDesktopBackground.dtd,v <-- setDesktopBackground.dtd new revision: 1.3; previous revision: 1.2 done Checking in browser/chrome/browser/shellservice.properties; /l10n/l10n/uk/browser/chrome/browser/shellservice.properties,v <-- shellservice.properties new revision: 1.5; previous revision: 1.4 done Checking in browser/installer/custom.properties; /l10n/l10n/uk/browser/installer/custom.properties,v <-- custom.properties new revision: 1.22; previous revision: 1.21 done Checking in toolkit/chrome/mozapps/downloads/downloads.properties; /l10n/l10n/uk/toolkit/chrome/mozapps/downloads/downloads.properties,v <-- downloads.properties new revision: 1.19; previous revision: 1.18 done
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.