0% found this document useful (0 votes)
42 views6 pages

Localization 21

Uploaded by

dacmac
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
42 views6 pages

Localization 21

Uploaded by

dacmac
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Using localized property values in the client interface

Configure the Translation access control list (ACL)


To allow select groups of users to view or modify translations for localizable
properties using the Localization button, you must create a new rule in the
Translation ACL.
Note The new rule is in addition to the dba group, Owning user, and World
entries in the ACL.

Using Access Manager, create a new Role in Group entry in the Translation ACL,
and grant translation privilege to the role in group.

This grants users translation access privileges. When these users log on to
Teamcenter, they see the Localization button in the properties dialog box next
to a property object that is localizable.
The following figure shows the Language Translations dialog box that is displayed
when you click the Localization button associated with the Name property.

For information about modifying access control lists, see the Access Manager Guide.

PLM00098 F Localization Guide 2-5


Chapter 2 Using localized property values in the client interface

Set preferences for localizing property values


Set the following preferences to localize property values in Teamcenter.
• TC_language_localization_display
To display translation information as read-only for properties that are
localizable, set the value to true.

• TC_language_localized_property_value_display
To specify the language to use for displaying localized property values, set the
value to one of the following locale codes:

Locale code Language


cs_CZ Czech
de_DE German
en_US English
es_ES Spanish
fr_FR French
it_IT Italian
ja_JP Japanese
ko_KR Korean
ru_RU Russian
zh_CN Chinese (as spoken in China)
zh_TW Chinese (as spoken in Taiwan)

• TC_language_localized_property_value_entry
To specify the data entry locale (master locale) of the logged-on user, set the
value to one or more of the following locale codes:
Note The master locale is the one used by the user to create/edit data in
a localized property.

Locale code Language


cs_CZ Czech
de_DE German
en_US English
es_ES Spanish
fr_FR French
it_IT Italian
ja_JP Japanese
ko_KR Korean
ru_RU Russian
zh_CN Chinese (as spoken in China)

2-6 Localization Guide PLM00098 F


Using localized property values in the client interface

Locale code Language


zh_TW Chinese (as spoken in Taiwan)

For more information about Teamcenter preferences and environment variables, see
Preferences and Environment Variables Reference.

Limit languages for data entry


Set the TC_language_data_entry preference to limit the languages in which data
can be entered in the Language Translation dialog box.
For example, to restrict data entry to English, French, German, and Spanish, set the
following values for the TC_language_data_entry preference:
• en_US

• fr_FR

• de_DE

• es_ES

In this example, if you log on to Teamcenter using a language that is not specified
for data entry, the system displays the following message, but does not prevent
you from logging on.
Your data language must be done using the following locales: English, French,
German, Spanish

Related topics
• Add the Localization button to properties

PLM00098 F Localization Guide 2-7


Chapter

3 Localizing operational data and


data model elements

Operational data and data model element localization . . . . . . . . . . . . . . . . . . 3-1

Operational data localization process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Export translations for review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Export untranslated master values for translation . . . . . . . . . . . . . . . . . . . . . 3-3

Review translations in the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Find untranslated master values in the rich client . . . . . . . . . . . . . . . . . . . . . 3-7

Import localization files using the rich client interface . . . . . . . . . . . . . . . . . . 3-8

Localization process in the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . 3-9


Introduction to setting language support . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Set the languages the template supports . . . . . . . . . . . . . . . . . . . . . . 3-10
Change the languages the template supports . . . . . . . . . . . . . . . . . . . 3-10
Set the master locale for the template . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Add a locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Introduction to setting display names . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Change display names for business objects and option types . . . . . . . . 3-16
Set display names for properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Set display names for lists of values (LOVs) . . . . . . . . . . . . . . . . . . . . 3-18
Validating localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Add the Localization button to properties . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Migrate a custom template to the newer language framework . . . . . . . . . . 3-22
Migrate property and relation names . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Create a default localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Import localization files using the Business Modeler IDE . . . . . . . . . . . . . 3-24

PLM00098 F Localization Guide

You might also like