translations need string type and context
Bug #126244 reported by
Michael Z
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
To reliably translate a string, a translator needs to know what it is (error message, heading, field label, instructions to user), and its context.
For example, to translate the string "login", I have to know whether it is
* Synonym for the noun "username" or "login ID".
* Heading for a log-in page.
* Instructions to user "log in" (imperative verb).
Possible solutions:
* Let the developer label each string using a pop-up menu with choice of type (e.g., "error message", "heading", "field label", "help text").
* Let the developer enter a label within their own devised schema for text in the program (e.g., "user instructions", "login screen", "network error messages", "preferences screen").
Revision history for this message
| Данило Шеган (danilo) wrote | #1 |
| Changed in rosetta: | |
| status: | New → Invalid |
To post a comment you must log in.
This can already be provided by developers through "translator comments" (look through gettext documentation if you need help) or through message "context". Please file bugs against applications instead.