After the multilingual user interface on your PPM instance, users can select their session language from the Language list on the logon page. The default session language displayed in the Language field at logon is the locale setting configured for the Web browser. If PPM does not support the preferred language set for the browser, the system language becomes the default session language. To use a language other than the default to interact with PPM, users must select it when they log on to PPM.
Note: For more information about the session language, see Introduction to Multilingual User Interface in PPM Center. For more information on how to log on to PPM, see the Getting Started guide.
The languages available in the Language list depend on the language packs deployed on the system. Language packs replace the English language text in the user interface with text in a different language. For more information about language packs, see the Installation and Administration Guide.
For the session language that a user selects, the system tries to display all text attributes in the user interface in the selected language. This includes all static boilerplate text in the interface, as well as custom attributes. However, translations may not exist in the selected language for all custom attributes. Attributes that are not translated are displayed in the language in which they were defined.
If a user cannot work with a form in PPM, it is likely that the underlying configurations have not yet been translated into the user's session language. For example, if activities have been translated to your language, the names and descriptions of activities are displayed in the user interface in your session language.
Note: When you create a new configuration, its definition language is implicitly set to your session language. For more information about session and definition languages, see Introduction to Multilingual User Interface in PPM Center.
Custom drop-down fields and custom auto-complete fields validated by "List" and "SQL - Custom" behave the same in the MLU, as follows:
If a custom drop-down/auto-complete list has multiple values, then a drop-down/auto-complete field with an existing value is shown in your current session language, even if your session language is different than the language in which the value was originally selected from the drop-down/auto-complete list.
Example. A custom drop-down/auto-complete list with multiple values has been created for requests. A user who logs on to PPM in a German language session creates a request, and in doing so, selects a value for the custom drop-down/auto-complete list. A different user logs on to PPM Center in a Korean language session and opens the new request, which was defined in German. The value in the drop-down/auto-complete field is shown in Korean.
Note: PPM does not support auto-complete fields validated by "SQL - User" in the MLU.
For more information, see Translating Auto-Completes and Drop-Down Lists for Requests.
To ensure that a SQL drop-down/auto-complete field behaves correctly,
- In the PPM Workbench, open the request type which contains the drop-down/auto-complete field.
On the Fields tab, select the drop-down/auto-complete field and click Edit.
The Field: <Field Name> window opens to the Attributes tab.
Note: If the drop-down/auto-complete field is a column of a table component, select and edit the table component.
In the Search Validation field, specify a list validation which contains:
- All the values potentially returned by the drop-down/auto-complete field.
- Potential translations of the returned values. If translations are not provided, the returned values will be used.
Note: If a table component contains several SQL drop-down/auto-complete columns, the list validation should include values potentially returned by all the components together with translations of the returned values.
The column headers for Time Management portlets can be misaligned and displayed vertically when displayed in Asian languages such as Japanese. If this occurs, it is typically in "narrow" portlets.
If you are a PPM administrator, you can configure the column widths on a editable portlet definitions as follows:
Copying the seeded portlet definition that displays the misaligned column header text.
Adjusting the column width on the copied portlet definition.
Publish the new portlet definition for end users.
For information about how to copy a portlet definition, adjust portlet column width, and how to publish a portlet definition, see the document Creating Portlets and Modules.