Saltar al contenido principal

Using the Repository

The repository is a multilingual dictionary filled in by the user (translator) and served for (semi) automatic translating. This tool is particularly useful for translators working on applications with similar interface elements.

The repository structure

You may think about the repository as the table, where the columns are the languages, and the rows are the translations of the same string. The repository form displays this structure visually.

Using the repository

Selecting the repository

You may have several different repositories for different purposes. Select the "Repository | Open repository..." menu item to choose the repository (.lr file) you want to work with.

The path to the currently selected repository is stored in the Registry. If no information or repository files are in the mentioned folder, then Language Manager creates a new empty repository in the "<LocalizerRootFolder>\Repository" folder.

Note: If you need to copy or move the repository to another folder, note that it consists of two files - .lr and .mem.

Translating cells using the repository

The main goal of the repository is to simplify the translation process.

To translate the selected cells with a value stored in the repository, choose the "Repository | Translate cell" menu item. For each selected cell, the program searches the repository for the translations of the native value in the grid row. If only one translation was found, Language Manager changed the cell value. Otherwise, if there are several suitable translations, the special dialog "Translate with repository" lets the user select one of the translations.

How does it search the repository?

First, the Language Manager tries to find in the repository the language that corresponds to the native language. If it's not found, then LM searches for its "next-of-kin" (i.e., "English" for "English (Canada)" or "English (United States)" for "English").

Then we find in the repository the language that corresponds to active language. The procedure is the same.

The found native language is searched for the native string - first case sensitive, then, if not found, insensitive.

All nonempty translations of the found entries of native string results from the search.

Use the "Repository | Translate language" menu item to translate all the values of the current language with values stored in the Repository. The program searches the Repository for the translations of the native language values in the corresponding rows. It does the same as described above for each string of the language file.

A "Repository" tab in the "Options" dialog allows you to manage the repository behavior. For example, you can choose to translate all strings or just untranslated ones, ask the user which translation to use, automatically put the first found translation, etc.

If "Smart Repository" is turned on, it means that for items with some "trailers," the repository can contain a significant part to let the item be translated. E.g., in the repository, you have an entry:

English: "Close"

German: "Schliessen"

When you have a project that has an entry "Close ->" it will get translated automatically to "Schliessen ->"

If the "Indicate availability" option is turned on, you will see a special mark ( or ) in the cell if it has an appropriate translation in the Repository.

Packing the repository

When you add/delete rows and languages to/from the repository, it may contain some empty and duplicate rows. Select the "Repository | Pack" menu item to delete extra rows. |