Firefox / Xulrunner better explanations for command / access key translating
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Carlos Perelló Marín |
Bug Description
Hi. There are two types of translatable single character strings in xulrunner / firefox strings. They should have a better tips for translators.
1. Command key (*.key, *.commandkey)
They are the shortcuts (eg. Ctrl + KEY), and often they can be easily left alone. The text besides those should say eg.:
"Select the shortcut key that you want to use. It should be translated, but often shortcut keys (for example Ctrl + KEY) are not changed from the original. If a translation already exists, please don't change it if you are not sure about it. Please find the context of the key from the end of the "Located in" text below."
2. Access key (*.accesskey)
These are the acc_ess keys, and these should be always translated. The text should say eg.:
"Select the access key that you want to use. These have to be translated, and they have to be translated in a way that the selected character is present in the translated string of the label being referred to, for example "i" in "Edit" menu item in English. If a translation already exists, please don't change if you are not sure about it. Please find the context of the key from the end of the "Located in" text below."
Changed in rosetta: | |
assignee: | nobody → carlos |
importance: | Undecided → High |
milestone: | none → 1.2.4 |
status: | New → Confirmed |
Changed in rosetta: | |
status: | Confirmed → In Progress |
Changed in rosetta: | |
status: | Fix Committed → Fix Released |
Fixed in RF 6183