Skip to content

Custom Translations

In addition to showing the user interface in multiple languages, GS also provides the ability to translate the names of some entities. This can be used, for example, to show the names of Defects in the user's native language.

GS currently supports English and Spanish.

Question

Is there another language you want us to implement? Let us know by contacting support.

A view of the Custom Translation page. Spanish translations have been added for Shift, Operator, Line, and Machine Traceability.

Creating Translations

When a new Custom Translation is added, it creates a new Translation Key. This key will be displayed for any language which does not have a translation provided. This allows setting up the site in any language and providing Custom Translations where appropriate.

For example, if Traceability were originally set up in Spanish, Custom Translations could be provided for the English values.

A view of the Custom Translation page. Spanish translations have been added for Shift, Operator, Line, and Machine Traceability.

Any translatable field in GS which has been set to the provided translate key will automatically be translated into the User's language. If nothing is provided for a language, then the original translate key will be displayed.

Disambiguating Translations

Sometimes a single word can be translated in multiple ways depending on the context. In these cases, it may be desirable to add additional context to the translate key and provide translations for every language. For example, the word "Bass" is ambiguous in English. If translations were needed for both a Bass Guitar and a Bass fish, it could be set up by providing additional context.

A page showing translations for "Bass (Guitar)" and "Bass (Fish)". Both English and Spanish translations are provided, with English translating both to just "Bass".

When setting up an entity which allows translations, the field can be filled in with the disambiguated translate key.

A page showing the creation of a Part with the name filled in as "Bass (Guitar)". Below the field are translations which say "English: Bass" and "Spanish: Bajo".

When this part is viewed in other contexts, it will have the translated value in all languages.

A page showing a list containing a single part. The part's name is "Bass".

Inline Translations

Any text field in GS which has a Translate button next to it may have Custom Translations applied directly. This is a shortcut for visiting the Custom Translations page and adding a new translate key.

The new Traceability page with an arrow pointing to the Custom Translation button next to the name field.

An overlay with language inputs for the "Operator" translate key.

If a field has a translation applied to it, those translations will appear below the field.

The new Traceability page with the name field filled in. There is a Spanish translation directly below the name field.

Rich Text Translations

Certain Rich Text fields on the site may also be translated. The current places where Rich Text fields may translated are:

Rich Text translations are stored with the Rich Text content being translated, and cannot be reused in multiple locations. Use the Language selector in the top right of the Rich Text Editor to switch between languages.

The new Traceability page with the name field filled in. There is a Spanish translation directly below the name field.

Import/Export

Column Header Required Allows Multiple Description
Translate Key Required No The key used to identify this translation
{Language} Optional Yes, one per language The translation for this language. If not provided, the translate key will be displayed instead

See Also