| 3. Translation | ||
|---|---|---|
 |  | |
| 3. Translation | ||
|---|---|---|
| | | |
SUSE program texts are translated to a number of languages. Because of this, it is very important to make program texts translator-friendly. It is unlikely for the translators to have access to the newest program. All they have is the information provided by the po files.
Different languages require different structures and orders. Splitting a text into multiple strings causes problems and confusion for translators and proofreaders. Never split strings.
It must be possible for translators to change the order of variables. The Qt-style numbered variables make this possible.
Include comments for translators whenever a string might be unclear to the translator. One-word strings can be confusing if the word can have multiple meanings or be different parts of speech. For these, provide a comment describing the meaning or context of the string.
When a string includes a variable, provide a comment explaining what will
replace the variable in the final string. Also provide comments for macros
other than &product;.
For the YaST to-do list-like lists of what YaST does in order or similar items, mark them progress stages.
Never translate the macro &product;. It is
replaced with the name of the product on which YaST is run. This can be SUSE
Linux, Novell Linux Desktop, or any other product.
"Progress stages" are to-do list like-items that display the steps a program will take. Translate these consistently for your language.
Do not translate any string or part of a string that comments specify should not be translated. This is done rarely.
If something is not clear, ask. Although the developers do their best to explain things, they may not realize that something is not clear.
| | | |
| 2. Rules for Specific Situations |  | 4. Resources |