Terminology (Wikipedia) is a group of specialized words or meanings, term entries, to be used to get more consistent translations. Termbase is a collection of term entries. A term entry contains a set of sections where each specifies the term in one language. For example, if we have a term entry that specifies the text used in the cancel button and the entry contains English, Finnish, German, and Japanese sections, the term would look like this:
Each entry and section can have several optional properties that give extra information about the entry or section. For example, there could be term location property that contains the Push button to indicate that the term is used as a button caption. Translations in glossaries are considered to be of high quality and carefully checked. This is why it is recommended to use them instead of your custom translations. Terminology is used to make translations consistent.
Termbase is a database where you can add new items, import items from terminology files, edit existing items, and remove items. Soluling supports two kind of termbases:
|Database termbase||A database that contains term data in a Soluling termbase structure. Initially, Soluling contains one empty local termbase.|
|Cloud termbase||A termbase that locates on a Cloud Termbase. It implements the same features as above local termbase, but the actual termbase exists on the cloud, making it easily accessible to all users of your localization team no matter where they locate.|
In addition to termbases, you can also add glossaries. Unlike termbases, glossaries are read-only. You can not modify them but consume them. Soluling supports the following glossary formats:
TermBase eXchange file. This is the recommended format because it is the only file format that is designed to store terminology data.
Translation Memory Exchange file.
A text file that contains terms. Regular expressions are used to define the format.
Excel or OpenDocument spreadsheet file that contains terms.
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 language-specific zip file that contains several glossaries from the MSDN download page. Most recent Microsoft glossaries are in TBX format.
Comma-separated values file that contains terms.
Database that contains terms.
When you install Soluling, the setup creates a local database termbase in a local SQLite database and adds that into Soluling's termbase list. The termbase is initially empty. You can import terminology data into the termbase from various sources.
You can have multiple database termbase. In addition, you have any number of cloud termbases. However, if you have several glossaries added into the glossary list, they might slow down the glossary engine. In that case, it recommended to remove the glossaries and import them into a termbase. Because termbase works on a database it can cope with very large term count.
If you want to maximize the terminology speed, keep only the default local termbase and import all your existing glossaries into the termbase. If you want to share the same terminology with multiple users, add a server database termbase (e.g. SQL Server or MySQL) or a cloud termbase and import all your existing glossaries into that termbase.
Soluling uses spell checkers for stemming that is needed when finding terms in your text.
What is the difference between a termbase, translation memory, existing translations, and machine translator?