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.

Provide an appropriate comment for translators when a string should be limited to a certain length.

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.

Unless otherwise marked in comments, strings that do not include HTML-like markup are limited to 78 characters. Error messages, warnings, and other pop-ups should be limited to 54 as much as possible. When necessary, create additional line breaks with \n.