Document home

Existing Translations

Existing translations or translation storage is a collection of translations. It is either a file or a database. The translations in translation storage contain certain terms or sentences in two or more languages. Soluling handles translation storage as a read-only item. It reads a translation from the translation storage but does not modify them.

Translation storage formats

Soluling supports the following translation storage formats:

Translation storage Description
Database

Database that contains translations.

Excel

Excel or OpenDocument file that contains translations.

TMX

Translation Memory Exchange file.

XLIFF

XML Localization Interchange File Format file.

In addition to the above glossaries Soluling supports the following legacy storage formats:

Translation storage Description
Binary file

Binary file that contains translations.

CSV

Comma-separated values file that contains translations.

Delphi translation repository

Delphi's translation repository file.

EDICT dictionary

EDICT dictionary file (home page)

Microsoft Translation and UI Strings glossary

Microsoft's legacy glossary file that contains terms and translations used by Microsoft products. Files use CSV format and .csv file extension. You can download a language-specific zip file that contains several glossaries from the MSDN download page. Most recent Microsoft glossaries are in TBX format and are also served through an API.

PO

PO file pair. If you have two PO files that contain the same items, but in different languages, you can use the files as translation storage.

Text file

Regular expression defined text file that contains translations.

Using a translation storage

You can import translation from translation storage into your project file. Translate sheet in the ribbon bar contains Import and Export section. Click Import file if your translation storage is a file. Click Import database if your translation storage is a database. In both cases, the application starts the Import Wizard that lets you specify the translation storage and the import options.

What is the difference between a termbase, translation memory, existing translations, and machine translator?