Translation

This topic explains how to define the NLS translation of vocabulary elements that can be displayed in different user experiences including native or web clients. Because vocabulary elements may be displayed in various user-experience including Native or Web clients, they have to translated.

This page discusses:

In the RDF File

To do so, use the <rdfs:label xml:lang="en">[label]</rdfs:label> construct.

Using External Files

Note: The use of external files for translation purposes is possible on-premises only.

In general, for a given vocabulary, named "XXX", the NLS translation of pertaining elements must be delivered in a separate file named PLMVocabulary_XXX.properties and located in the runtime-view apache-tomcat/webapps/ematrix/WEB-INF/classes.

If any, customized NLS definition for a DS vocabulary can be delivered through a file with the same name but appended with suffix_custom, for example, PLMVocabulary_ds6w_Custom.properties.

Based on the files naming conventions quoted above, the search of NLS entries occurs in the following order:

  • First, PLMVocabulary_XXX_Custom
  • Then, PLMVocabulary_XXX.

For a Predicate
Enter <predicate.predicate_name>=<predicate_nls_string>. Note that predicate. is a keyword.

Example in a .properties file: project=Collaborative Space.

For Predicate Enumerated Values
For a predicate of a XXX vocabulary, it may be useful to define a set of help-values along with a range axiom. In this case, the NLS translation of these values can be defined in the vocabulary NLS file, PLMVocabulary_XXX.properties with the following format: <predicate_name>.<val1>=<val1_nls_string>.

For example, in a file_fr.properties: 

country=Pays
country.UnitedStates=Etats Unis
country.Germany=Allemagne