SIEMENS TeamCenter PLM guide
March 7, 2017 | Author: Mihai Ispir | Category: N/A
Short Description
Download SIEMENS TeamCenter PLM guide...
Description
SIEMENS
Teamcenter 11.2 Teamcenter Localization PLM00098 • 11.2
Contents
Overview of Teamcenter localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is Teamcenter localization? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Teamcenter locales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Localizing property values in Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing, editing, and adding translations for a property using the Localization button Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . .
7 8 8 9 10 11
Displaying and deploying localized versions of Teamcenter . . . . . . . . . . . . . . . . . . . . . . 1-1 Localization process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying localized versions of Teamcenter on your client workstation Configuring localized display of the Teamcenter client interface . . Teamcenter localizations provided by Siemens PLM Software . . . Choose a display language for the thin client . . . . . . . . . . . . . . Choose a display language for the rich client . . . . . . . . . . . . . . Example: Displaying the Teamcenter rich client in German . . . . . Switching between display languages . . . . . . . . . . . . . . . . . . . Add multibyte character support in an English rich client . . . . . . . Deploying client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . Update thin client localized text . . . . . . . . . . . . . . . . . . . . . . . . Create a thin client localization . . . . . . . . . . . . . . . . . . . . . . . . Convert the thin client user interface for Hebrew . . . . . . . . . . . . Update rich client localized text . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . .
1-1 1-1 1-1 1-2 1-2 1-4 1-5 1-7 1-7 1-7 1-7 1-8 1-9 1-10
Using localized property values in the client interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Property value localization overview . . . . . . . . . . . . How do you know if a property is localizable? . . . . . . Who can enter localized property values? . . . . . . . . Enter localized property values . . . . . . . . . . . . . . . . Searching for localized property values . . . . . . . . . . Configuring property value localization . . . . . . . . . . . Create the Translation group and Translator role . Configure the Translation access control list (ACL) Set preferences for localizing property values . . . Limit languages for data entry . . . . . . . . . . . . . . Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . .
. . . . . . . . .. .. ..
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
2-1 2-1 2-1 2-2 2-3 2-3 2-3 2-4 2-5 2-6 2-7
Localizing operational data and data model elements . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Operational data and data model element localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Operational data localization process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Export translations for review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
PLM00098 11.2
Teamcenter Localization
3
Contents Contents
Export untranslated master values for translation . . . . . . . . . . . Review translations in the rich client . . . . . . . . . . . . . . . . . . . . Find untranslated master values in the rich client . . . . . . . . . . . Import localization files using the rich client interface . . . . . . . . . Localization using the Business Modeler IDE . . . . . . . . . . . . . . Localization process in the Business Modeler IDE . . . . . . . . Setting language support . . . . . . . . . . . . . . . . . . . . . . . . . Setting display names . . . . . . . . . . . . . . . . . . . . . . . . . . . Add the Localization button to properties . . . . . . . . . . . . . . Migrate a custom template to the newer language framework Migrate property and relation names . . . . . . . . . . . . . . . . . Create a default localization . . . . . . . . . . . . . . . . . . . . . . . Import localization files using the Business Modeler IDE . . . . Localization and live update . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . .
3-3 3-5 3-7 3-8 3-9 3-9 3-9 3-18 3-25 3-27 3-28 3-31 3-31 3-32
Non-English locale environment settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 Teamcenter localizations provided by Siemens PLM Software Verify that your locale is supported . . . . . . . . . . . . . . . . . . Configuring a UTF-8 environment for Teamcenter . . . . . . . . Overview of UTF-8 configuration . . . . . . . . . . . . . . . . . Configure UTF-8 environment settings . . . . . . . . . . . . . Configuring a non-UTF-8 environment for Teamcenter . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
A-1 A-2 A-2 A-2 A-5 A-6
Special considerations when localizing Teamcenter applications . . . . . . . . . . . . . . . . . . B-1 Audit Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Considerations when localizing Classification . . . . . . . . . . . . . . Installing localization template for Classification . . . . . . . . . . . . . Granting translation privileges . . . . . . . . . . . . . . . . . . . . . . . . Marking classification attributes as localizable . . . . . . . . . . . . . . Marking class attributes as nonlocalizable . . . . . . . . . . . . . . . . Exporting translations for Classification . . . . . . . . . . . . . . . . . . Understanding classification localization closure rules . . . . . . . . Electronic Design Automation (EDA) considerations . . . . . . . . . . . . Limitations on the ability to localize property values . . . . . . . . . . Limitations on locale characters . . . . . . . . . . . . . . . . . . . . . . . Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mechatronics Process Management . . . . . . . . . . . . . . . . . . . . . . . Sharing data with other sites using Multi-Site Collaboration or TC XML Schedule Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Structure Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data that cannot be localized in Structure Manager . . . . . . . . . . Localize revision rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. B-1 . B-1 . B-1 . B-2 . B-3 . B-4 . B-4 . B-4 . B-5 . B-7 . B-7 . B-8 . B-8 . B-8 . B-9 B-10 B-10 B-10 B-11 B-11
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1 Localization preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
4
Teamcenter Localization
PLM00098 11.2
Contents
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Figures Unicode homogeneous server platform configuration . . . . . . . . . . . . . . . . . . . . . . . . . A-4 ICSL10NExportClassHierarchy transfer mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
Tables Encodings for Oracle databases . . . . . . . . . Encodings for MS SQL databases . . . . . . . . Values for LANG and LC_ALL . . . . . . . . . . Environment settings on non-UTF-8 systems
PLM00098 11.2
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
Teamcenter Localization
3-14 3-15 . A-5 . A-7
5
Overview of Teamcenter localization
Before you begin Prerequisites
Depending on the type of localization you plan to do, Teamcenter administrator privileges may be required. •
On UNIX and Linux systems, the LANG and LC_ALL system environment variables must be set before you begin installing Teamcenter. Teamcenter Environment Manager (TEM) requires these settings. LANG and LC_ALL must be identical for installation tools to function properly.
•
Displaying localized versions of the standard Teamcenter user interface You do not need special Teamcenter privileges to deploy localized versions of Teamcenter.
•
Localizing property values in Teamcenter o
Administrator rights Business Modeler IDE users must be members of the database administrators (dba) group on the Teamcenter server. Use the Organization application in the Teamcenter rich client to add a user to the dba group.
•
Importing localization files You must have Translator role privileges to import translations.
Configure Teamcenter
You must configure Teamcenter to enable localization. •
Localized versions of the standard Teamcenter user interface Certain Teamcenter preferences are required to deploy localized versions of Teamcenter.
•
Localizing property values in Teamcenter You must set several Teamcenter preferences to deploy localized property valuesin Teamcenter.
PLM00098 11.2
Teamcenter Localization
7
Overview Teamcenter localization Overview of of Teamcenter localization
What is Teamcenter localization? Localization is the process of converting a program, such as Teamcenter, to run in a particular locale (a particular language spoken within a country) so that all text is displayed in the native language. The term localization often refers to the set of files used to display the deploy the translation. A locale represents a language and a country. For example, English is spoken in both the United States and England. However, there are differences in the English language between these countries. Therefore, there are different locale designators. Teamcenter supports English as spoken in the United States. When installing Teamcenter, it is automatically set to the en_US locale, where en is the English language identifier and US is the United States country identifier. The fr_FR locale is another supported Teamcenter locale, where fr is the French language identifier and FR is the France country identifier. Display names are user-friendly aliases for internal object names. Properties describe characteristics of a business object, such as name, serial number, and description. There are several interface components that can be configured in local languages. Teamcenter client user interface
When you purchase Teamcenter, you receive localization files that allow you to display the client interface in a number of standard languages (locales). To display the interface in these locales, you must install the localization files and configure the system environment and Teamcenter environment. Standard localization files do not have to be deployed, they must only be installed. You can modify the standard localization files to create your own localization of the Teamcenter interface. When you modify or create localization files, you must build and deploy them using Web Application Manager.
Property values (attributes)
Teamcenter can be configured to allow privileged users to specify localized values for business object properties. Some object property localization is available in the standard Teamcenter installation. For example, you can use the Localization button in Organization to add localized group names and in Query Builder to add localized query names and descriptions. You can configure most attributes and form fields to accept localized values.
Display names for data model components
You can modify the display name of standard and custom business objects, properties, and lists of values (LOVs) after they are created by using the localization table in Business Modeler IDE. This allows you to specify the name of the object in different languages or to simply change the name of the object in the default locale.
Supported Teamcenter locales A locale represents a language and a country. Teamcenter supports the following locales: •
en_US English as spoken in the United States
•
8
cs_CZ
Teamcenter Localization
PLM00098 11.2
Overview of Teamcenter localization
Czech as spoken in the Czech Republic •
fr_FR French as spoken in France
•
de_DE German as spoken in Germany
•
it_IT Italian as spoken in Italy
•
es_ES Spanish as spoken in Spain
•
ja_JP Japanese as spoken in Japan
•
ko_KR Korean as spoken in Korea
•
pl_PL Polish as spoken in Poland
•
pt_BR Portuguese as spoken in Brazil.
•
ru_RU Russian as spoken in Russia
•
zh_CN Chinese as spoken in China (Simplified Chinese)
•
zh_TW Chinese as spoken in Taiwan (Traditional Chinese)
Localizing property values in Teamcenter The Localization button allows localization administrators to enter localized text for property values. To place the Localization button on properties in Teamcenter, an administrator must use the Business Modeler IDE to set the Localizable property constant to true for those properties. Using the Localization button, you can perform the following tasks: •
View the existing localization text.
•
Modify the existing localization text.
PLM00098 11.2
Teamcenter Localization
9
Overview Teamcenter localization Overview of of Teamcenter localization
•
Add a translation value for a new locale without altering the master value of the property.
•
Remove a translation value without altering the master value of the property.
Viewing, editing, and adding translations for a property using the Localization button The Localization button provides an easy way for users to view, edit, and add translations for a given localizable property. For example, in the Query Builder application, you can select a query regarding employee information. Note
•
The Localization button appears by default in the following applications: o
Organization (site, group, and calendar)
o
Query Builder
o
Report Builder
o
Classification Admin
In addition, the Localization button appears on localized property fields. You must use Business Modeler IDE to create a customized template to localize the individual property fields. •
Only privileged users (with the Translation privilege set in Access Manager) can add and edit the translations.
The presence of the Localization button indicates the dialog box content can be localized. For example, if the master locale is set to English, you can add a translation for this employee information query. Using the Localization button, you can perform the following tasks: •
View the existing localization text.
•
Modify the existing localization text.
•
Add a translation value for a new locale without altering the master value of the property.
•
Remove a translation value without altering the master value of the property.
To localize the name of the saved query, Admin – Employee Information in the example, click the Localization button to the right of the Name box. The Language Translations dialog box is displayed. The master locale and master value are retained. Click the plus button (+) to add a localized value. Click the minus button (–) to remove a localized value. When adding a new value, you must add text in the following fields: •
10
Master Locale
Teamcenter Localization
PLM00098 11.2
Overview of Teamcenter localization
Displays the locale set for the site, for example, English. •
Master Value Displays the original text. This is the value that is stored when a new object is created. The content of this field can only be changed from the main dialog box.
•
Value Specifies the property value content.
•
Status Specifies the status of the localization. From the list, select one of the following: o
Approved The text change is approved for use.
o
Invalid The text change is not valid.
o
Pending The text change is pending approval.
o
Review The text change is in review.
•
Locale Specifies the locale. The list displays the locales that have been made available by the administrator, for example: o
French
o
German
o
Italian
o
Spanish
Related topics •
What's new in Teamcenter 11.2
•
Getting Started with Teamcenter
•
Frequently Asked Questions for Teamcenter
•
Teamcenter Basics
•
Thin Client
PLM00098 11.2
Teamcenter Localization
11
Overview Teamcenter localization Overview of of Teamcenter localization
•
12
Glossary
Teamcenter Localization
PLM00098 11.2
Chapter 1: Displaying and deploying localized versions of Teamcenter
Localization process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Displaying localized versions of Teamcenter on your client workstation Configuring localized display of the Teamcenter client interface . . Teamcenter localizations provided by Siemens PLM Software . . . Choose a display language for the thin client . . . . . . . . . . . . . . Choose a display language for the rich client . . . . . . . . . . . . . . Example: Displaying the Teamcenter rich client in German . . . . . Switching between display languages . . . . . . . . . . . . . . . . . . . Add multibyte character support in an English rich client . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
1-1 1-1 1-2 1-2 1-4 1-5 1-7 1-7
Deploying client localizations . . . . . . . . . . . . . . . . Update thin client localized text . . . . . . . . . . . . Create a thin client localization . . . . . . . . . . . . Convert the thin client user interface for Hebrew Update rich client localized text . . . . . . . . . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . .
1-7 1-7 1-8 1-9 1-10
PLM00098 11.2
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
Teamcenter Localization
Chapter 1: Displaying and deploying localized versions of Teamcenter
Localization process overview When you purchase Teamcenter, you receive localization files that allow you to display the client interface in a number of standard languages (locales). To display Teamcenter in these locales, you must install the localization files and configure the system environment and the Teamcenter environment. If you modify the standard localization files or create localization files for nonstandard locales, you must build and deploy the files using the Web Application Manager. In addition, you must perform the configuration tasks required to display a localized version of Teamcenter.
Displaying localized versions of Teamcenter on your client workstation Configuring localized display of the Teamcenter client interface Before users can choose the language (locale) in which the Teamcenter interface is displayed on their client machine, the locale must be installed on the server, and the following server-side administrative tasks must be performed: •
Define data entry locales. Set the TC_language_data_entry preference to define the locales for user data entry. Note
The locales you specify for this preference must be supported by your database encoding. •
Specify the default language for the Teamcenter server process. Set the TC_language_default preference to set the default locale in the event that no locale is passed.
•
Force the thin client to start up using the default language (specified by the TC_language_default preference) by setting the TC_language_force_thin_client_locale preference.
•
Configure system environment settings. You must set your operating system and Teamcenter environment settings for each locale to ensure proper display and data processing.
PLM00098 11.2
Teamcenter Localization
1-1
Chapter Displaying and deploying localized versions of Teamcenter Chapter 1: 1: Displaying and deploying localized versions of Teamcenter
Teamcenter localizations provided by Siemens PLM Software Siemens PLM Software provides localized versions of Teamcenter in the following languages: Language
Locale code
Chinese (Simplified)
zh_CN
Chinese (Traditional)
zh_TW
Czech
cz_CZ
English
en_US
French
fr_FR
German
de_DE
Italian
it_IT
Japanese
ja_JP
Korean
ko_KR
Polish
pl_PL
Portuguese (Brazilian)
pt_BR
Russian
ru_RU
Spanish
es_ES
Use the appropriate locale codes to deploy Teamcenter localizations or launch Teamcenter clients in a desired locale. If you provide your own localizations for locales not provided by Siemens PLM Software, use the appropriate Java standard locale codes similar to the locale codes in the preceding table.1 Localizing Teamcenter in Hebrew Siemens PLM Software does not provide a Hebrew translation but provides recommended configuration settings for Hebrew locales. In Hebrew locales, set the locale code to en_US. This allows data entry in Hebrew, but user interface text is in English.
Choose a display language for the thin client By default, the thin client displays in the language specified by your operating system locale settings. If you want to override the default language, you can choose the display language for the thin client. At each logon, you can choose between multiple languages, depending on your company's policy and installation. There are two ways you can specify the language: •
Specify the language in the URL. For example: o
To specify French, type http://myhost:7001/tc/webclient?lang=fr in the URL.
o
To specify Russian, type http://myhost:7001/tc/webclient?lang=ru in the URL.
1. Standard locale codes are composed of a two lowercase character language code from the ISO 639-1 standard, followed by an underscore, followed by a two uppercase character country code from the ISO 3166-1-alpha-2 standard.
1-2
Teamcenter Localization
PLM00098 11.2
Displaying and deploying localized versions of Teamcenter
Note
o
When specifying a language in the URL, use standard W3C locale identifiers.
o
Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, use host names in URLs wherever possible so the domain name system (DNS) can determine which IP address to use. If you must use IP addresses and your network uses IPv6 addresses, enclose the literal IPv6 address in square brackets, for example: http://[2001:db8:ffff:1:101:12ff:de13:1322]:9043/tc
•
Specify the language in your browser preferences. For example, in Microsoft Internet Explorer, perform the following steps: 1. Choose Tools → Internet options.... 2. Click Languages in the Internet Options dialog box. 3. Click Add in the Language Preference dialog box. 4. Click any language in the Add Language dialog box. 5. Click OK in the Add Language dialog box. 6. Click the language you want to see in the user interface in the Language Preference dialog box. 7. Click the Move Up button. The language you move to the top of the list in the Language Preference dialog box is the language you see in the user interface. 8. Click OK in the Language Preference dialog box. 9. Click OK in the Internet Options dialog box. 10. Log on and view the user interface in the language you chose. Note
An error message is displayed if the specified language is unavailable. Your ability to set the language for the thin client depends on the character set encoding of the Teamcenter server host and also the character set encoding of the Teamcenter database. Note
To prevent mixed-language display after you change the thin client display language, clear your web browser cache. This prevents the interface from displaying in mixed languages.
PLM00098 11.2
Teamcenter Localization
1-3
Chapter Displaying and deploying localized versions of Teamcenter Chapter 1: 1: Displaying and deploying localized versions of Teamcenter
Choose a display language for the rich client By default, the rich client is displayed in the language specified by the operating system. If you want to override the default language, you can choose the display language for the rich client. Note
•
Your ability to set the language for the rich client depends on the character set encoding of the Teamcenter server host and also the character set encoding of the Teamcenter database.
•
If you find that Asian multibyte characters do not display correctly in the rich client, set your system font to a font that supports Asian multibyte characters. For example, on Microsoft Windows systems, the Arial Unicode MS font can be set to Message Box to correct this problem. Similarly, if you find that Asian multibyte characters do not display correctly when you start the rich client using the native language (-nl) option, restart your system in the appropriate locale and set your system font to a font that supports Asian multibyte characters.
If you want to override the default language to launch the rich client in a desired language, add the -nl argument to the rich client launch command: •
Windows systems: TC_ROOT\portal.bat -nl locale-code
•
Linux systems: TC_ROOT/start_portal -nl locale-code
Replace TC_ROOT with the Teamcenter home directory, and replace locale-code with the desired locale code. For example, to launch the rich client Italian user interface, enter the following from a command prompt: •
Windows systems: D:\tc\rac\portal.bat -nl it_IT
•
Linux systems: /tc/rac/start_portal -nl it_IT
Alternatively, on Windows systems, you can customize the properties for the Teamcenter rich client desktop shortcut icon
to specify a desired language:
1. On your desktop, right-click the Teamcenter rich client shortcut icon
.
2. Choose Properties. A properties dialog box is displayed. 3. Click the Shortcut tab. 4. In the Target box, add an -nl argument to specify the desired language.
1-4
Teamcenter Localization
PLM00098 11.2
Displaying and deploying localized versions of Teamcenter
The -nl argument accepts a single string as value. The string must be one of the supported locale codes. For example, to run the rich client Italian user interface: D:\tc\rac\portal.bat
becomes: D:\tc\rac\portal.bat —nl it_IT Note
To prevent mixed-language display the next time you run the rich client after you change the -nl argument value, or after you change your operating system locale, delete the Teamcenter directory under your user directory. •
On Windows clients, delete: C:\Documents and Settings\user-name\Teamcenter
•
On Linux clients, delete: $HOME/Teamcenter2
Example: Displaying the Teamcenter rich client in German To change the Teamcenter display from English to German by using the Properties selection on your Teamcenter desktop shortcut, perform the following steps: 1. On your desktop, right-click the Teamcenter rich client shortcut icon
.
2. Choose Properties. A properties dialog box is displayed. 3. Click the Shortcut tab. 4. In the Target box, add an -nl argument to specify the desired language. The -nl argument accepts a single string as the value. For example, to run the rich client German user interface: D:\tc\rac\portal.bat
becomes: D:\tc\rac\portal.bat —nl de_DE
The German Teamcenter Properties dialog box appears.
2. $HOME is your user home directory.
PLM00098 11.2
Teamcenter Localization
1-5
Chapter Displaying and deploying localized versions of Teamcenter Chapter 1: 1: Displaying and deploying localized versions of Teamcenter
5. Click OK. Teamcenter displays in German.
1-6
Teamcenter Localization
PLM00098 11.2
Displaying and deploying localized versions of Teamcenter
Switching between display languages When you install Teamcenter, the client interface displays in the language specified by your operating system locale settings. Teamcenter includes localization files for a number of locales. After the localization files are installed and the operating system and Teamcenter configuration tasks are complete, you can easily switch between languages on your client machine. You can: •
Choose the display language in the thin client, by specifying the language either in the Teamcenter URL or in your browser preferences.
•
Choose the display language in the rich client, by either: o
Extending the command line.
o
Changing the Properties selection on your Teamcenter desktop shortcut (Windows systems).
Add multibyte character support in an English rich client 1. In the rich client \rac\plugins\configuration_config-name directory, create the customer.properties file, if it does not already exist. Note
Do not save the customer.properties file in unicode or UTF-8 format. The customer.properties file must be in the default format (for example, ANSI) to be read successfully by the rich client. 2. Open the customer.properties in a plain text editor. 3. Add the following line to the file to set the UseDefaultSwingFonts property. UseDefaultSwingFonts=true
4. Save the file and exit the text editor. 5. Change to the rac\registry directory. 6. Run the genregxml.bat utility to register the change. Note
When you run Teamcenter in a multibyte environment, make sure the TC_XML_ENCODING environment variable is set to UTF-8 and the UGII_UTF8_MODE environment variable is set to 1.
Deploying client localizations Update thin client localized text The thin client text server files reside under the Teamcenter application root directory in the \lang\textserver\locale-code directory (Windows systems) or the /lang/textserver/locale-code
PLM00098 11.2
Teamcenter Localization
1-7
Chapter Displaying and deploying localized versions of Teamcenter Chapter 1: 1: Displaying and deploying localized versions of Teamcenter
directory (UNIX/Linux systems). If you change one of the text server XML files (*_locale.xml and *_errors.xml), regenerate the webstrings.xml file: 1. Change to following directory: •
Windows systems: WEB_ROOT\staging-location\webapp_root\teamcenter\dhtml\common\intl
•
UNIX and Linux systems: WEB_ROOT/staging-location/webapp_root/teamcenter/dhtml/common/intl
2. Copy the webstrings.xml file to the language directory. 3. Regenerate the web tier application (file-name.war) and deploy in an application server. 4. Change the header encoding of the webstrings.xml file to the appropriate language-specific character encoding value, for example, Shift-JIS for Japanese. Note
After you complete these steps, clear your web browser cache before you launch the thin client.
Create a thin client localization If you localize the thin client into a language not provided by Siemens PLM Software: 1. In the Teamcenter application root directory, create a directory for the new language under the \lang\textserver\ directory (Windows systems) or the /lang/textserver/ directory (UNIX and Linux systems). For example, if you localize the user interface for Hebrew, create the iw_IL directory. 2. Copy all files from the en_US directory to the new language directory. 3. In the new language directory, translate all XML files to the new language. Note
Make sure the encoding specification at the top of each XML file matches your system encoding when you save the file. Also, make sure the encoding specified supports the desired locale. For Hebrew on Windows systems, the encoding specification should resemble the following example:
4. Edit the weblocal_locale.xml file in the new language directory to change the value of the web_local_lang parameter from en to the new language name. For example, if you localize the user interface for Hebrew, change the web_local_lang parameter to he: web_local_lang: exported "he";
1-8
Teamcenter Localization
PLM00098 11.2
Displaying and deploying localized versions of Teamcenter
5. In the \lang\textserver\no_translation directory (on Windows systems) or the /lang/textserver/no_translation directory (on UNIX/Linux systems), locate the textserver_text.xml file and open it in a plain text editor. 6. Locate the following key for the new language:
View more...
Comments
