Available Languages
The Available Languages enumeration must be populated with the list of all languages to be used in the system for authoring, translation, and display of translated text.
New entries can be added to the enumeration for languages not already represented. The Internal Name property of all entries in the Available Languages enumeration must be a supported language tag.
When creating a new enumeration entry for Available Languages, the system validates the value entered for the Internal Name property.
• If a non-supported language tag is entered as the Internal Name property value, the system displays an error message.
• If the value entered for the Internal Name property can be converted to a supported language tag, the proposed language tag is presented in the error message.
• If a supported language tag entered as the Internal Name property value is already in use on an existing Available Languages enumeration entry, the system displays an error message identifying the display name of the existing enumeration entry.
Windchill supports a subset of the BCP 47 standard for language tags. The supported syntax for a language tag is:
<language code>
or
<language code>-<country code>
The <language code> must be lower case, while the optional <country code> must be upper case or numeric.
Supported language codes meet the following specification:
• Use an ISO 639–1 language code (two letters), if one exists. Otherwise, use an ISO 639–2 language code (three letters).
The list of ISO 639–1 and ISO 639–2 language codes are found here:
• If a language code has been deprecated, use its active replacement. For more information, see:
Supported country codes meet the following specification:
• Use official ISO 3166 alpha-2, alpha-3, or UN M.49 numeric–3 country codes.
For more information on ISO 3166 alpha-2 and alpha-3 country codes, see:
For more information on UN M.49 numeric–3 country codes, see
• Use an alpha-2 code, if one exists. If an alpha-2 code does not exist, use an alpha-3 code. If neither of these exist, then use the numeric code.
 |
User-assigned ISO 3166–1 alpha-2 codes (AA, QM to QZ, XA to XZ, and ZZ) and numeric codes (900 to 999) are supported country codes.
|
Configuring New Language Codes For Search Indexing
If you add a new entry to the Available Languages enumeration for a language, and then add that entry to the Available for selection table of the Source Languages or Target Languages subenumerations, you must complete the following configuration steps for that language to be correctly indexed and searched.
1. Create conf_<lang_tag>_.xml:
a. Create a file named conf_<lang_tag>.xml in the following location: <Index_Search_Home>\SolrServer\solr\server\solr\wblib\conf, where <Index_Search_Home> is the installed location on your index search server.
Replace <lang_tag> with the supported language tag which you added as the internal name of the new entry in Available Languages. This language tag must meet the criteria for a supported language tag described previously in this topic.
b. Add the xml entity entry for the conf_<lang_tag>.xml file in the following file: <Index_Search_Home>\SolrServer\solr\server\solr\wblib\conf\schema.xml
2. Define the Solr field type:
a. Refer to the sample schema.xml file provided by Solr at the following location:
b. Define the Solr field type in the conf_<lang_tag>.xml file.
c. For a language for which no specific tokenizer is available, use the default field type of text. The text field type uses the English tokenizer.
d. Add the appropriate Solr filters such as solr.LowerCaseFilterFactory or solr.RemoveDuplicatesTokenFilterFactory.
e. Refer to the existing field type definitions under the same directory as the conf_<lang_tag>.xml file for more information.
3. Define the Solr dynamic field using the field type defined in step 2. The field name must be *_<lang_tag>, where <lang_tag> is a supported language tag as described previously in this topic.