Translation UX/Specification

List of messages


Summary. Messages are presented in a list using white background for messages requiring processing (untranslated messages but also messages that need some kind of revision) and gray for those that not require processing.

Each message is composed by the original message, the translated message (if any) de-emphasized using gray text, and a status label (more on this below).

Rationale Aspects to consider
 * Emphasize messages that require actions.
 * Facilitate scannability. Messages are represented in one line. As discussed below, other requirements (ease of proofreading) may conflict with this.
 * Truncating messages becomes a problem when translating and proofreading long messages (typically from page translations).
 * Although message codes are not normally required, some scenarios will require them.
 * Part of the scenarios can be solved by searching to a specific code, but not all of them.

Label system

 * Only one label is shown for each message, being the precedence "To review" > "Outdated" > "Translated".

Translation dialog layout


Rationale.
 * Provide a compact layout based on two columns.
 * Screens are getting wider.
 * Most messages are short.
 * Long messages lack suggestions, so they can use more horizontal space when needed.
 * Distribution is based on a 12 column layout where translation area uses 7 columns and the help area 5.