Home | Index

r3 User Guide

Translations Tab

The translations tab lets you easily add, search for, translation text, and manage translation inheritance.

Adding Translations

To add a translation:

  1. In location, set the product and intl for the translation, and click change.

  2. In add translation, enter the source text and its translation, and click add. A red message tells you that your text has been added to the translation and its searchpath location.

    Figure 5.4. Adding a Translation

    Adding a Translation

Searching For Translations

You can search for translations by source text or by translation text by entering the search term, choosing the appropriate search option, and clicking search. r3 responds with the location of the translation, and the manage translations view displays the term and its source or translation. The default search behavior is a fuzzy search. To enforce a strict match, select exact. Also note that you can filter your searches on translation status, approved vs. unapproved. (When you change a translation, r3 automatically sets it to approved. You can later filter out approved translations and concentrate on those that still need work.)

Figure 5.5. Searching for a Term

Searching for a Term

Managing Translations

The manage translations view displays translation text for a specific product and intl in groupings of 10. You can edit the translation text within this view and click update to save the changes.

Figure 5.6. Managing Translations

Managing Translations

If you set an inheritance path for translations, the path displays when you click show to display translation information. You can delete a translation by clicking delete. The show view also enables you to move the translation inheritance to a different location in the searchpath.

Figure 5.7. Managing Translation Inheritance

Managing Translation Inheritance

In the example above, fromage has been added to the translations in the searchpath cookery/fr/generic. By clicking move you can copy fromage to the translations in the searchpath cookery/us/generic (it appears in both searchpaths).

[Note] Note

The translation rule is: "Copy on specialize, move on promote." If you're specializing down from a generic context removing the original translation (in our case, the translation in cookery/us/generic) would delete it for any dimensions inheriting from it. However, when you promote a translation up the searchpath you should remove the current instance.