The predefined process templates support translation of
strings. You can modify a process template that you create so that
it can be translated to support multiple locales.
About this task
To make a process template translatable, replace translatable
property strings with property keys (%
key.
n format).
Then create locale-specific files in which you map the property keys
to the translated text strings. Attach the locale-specific files to
the process template.
Examples of strings that you should replace
with property keys include the following:
- Dashboard and dashboard viewlet descriptions
- Dashboard titles and categories
- Dashboard viewlet titles
- Follow-up action names and descriptions
- Path to the process content (if applicable)
- Precondition names and descriptions
- Process names, descriptions, and summaries
- Role names and descriptions
- Work item aliases
- Work item enumeration literals
- Work item query names and descriptions
- Work item quick information titles
- Work item states, actions, and resolutions
- Work item type names
- Workflow names
Not all strings are suitable for translation. Do not replace
strings for the following fields:
- ID fields, such as process IDs, work item IDs, and role IDs
- Fields with Boolean values or color values
- Fields that refer to other fields
- Fields within work item queries
- Trim values within viewlet elements
- True and False fields
For more examples of strings to replace with property
keys, see the predefined process templates.