In Lingo you can use concept-oriented terminology databases to make your translation work easier and quicker. Termbases allow you to create, manage, and reuse multilingual terminology from a single storage area. This system automatically displays previously translated words from your termbase during the translation process, thus improving the reliability of translations.
A termbase is more powerful than a dictionary. The idea behind a termbase is to create a database of words and phrases that you never need to translate again.
Features and benefits of termbases in Lingo include the following:
You must have SQL installed to take advantage of server translation memory (TM) and termbases in Lingo. The following types of SQL are supported: SQLite and SQL Express. If you are new to Lingo, TM, and termbases, you probably want to use SQLite, purely because of its simplicity. See Creating Termbases.
This is a self-contained relational database system that is in the public domain. In Lingo, SQLite is intended for local TM databases and termbases, not those that reside on an external server. SQLite is easier and faster, just not quite as robust as SQL Express.
SQLite is automatically installed during the process of installing Lingo. For more information about this database system, see www.sqlite.org.
By default, the location for SQLite databases is in Documents\Lingo Translation Memories on your computer. However, you can choose a different location if you like.
SQL Server Express is designed to be used on a server with Lingo. To download and install the latest version of SQL Server Express, go to http://www.microsoft.com/downloads/.
The top section of the Termbase Editor contains a filter and a grid listing the terms in each language.
When you use the Filter field, the list shortens accordingly to show only the terms that match the search criteria.
example
Lets say you have a termbase that looks like this:
You want to see only the rows containing the word "Motorcycle." So you type that term into the Filter field and click .
The grid changes to show only the row that contains that word.
When you are finished, you click to empty the Filter field and return the grid to its previous list.
The grid shows all of the terms and their corresponding languages in the termbase.
Each cell may contain multiple terms. And the entire row of terms and languages is called a "concept."
Note: The idea of a concept in a termbase should not be confused with the concept files that you may import from Flare project.
The lower-left corner of the Termbase Editor displays information about the terms from the selected row in the grid above.
There is a tab for each language with the term. The information in that tab is unique to that term in that language.
You can add a new term by clicking . You can remove a term by selecting it and clicking . And you can add a term in a new language by clicking the plus tab.
You can use a button in the local toolbar to add multiple terms to a termbase via a batch. For example, you might need to add a list of corporate terms from an email. The quickest way to do this is to use the Batch Add Terms to Termbase dialog to enter all of those words and their translations in the target language.
You can import and export TermBase eXchange (TBX) files. TBX is an open, XML-based standard used for exchanging structured terminological data. It has been approved as an international standard by the Localization Industry Standards Association (LISA) and the International Organization for Standardization (ISO). One difference between a TBX file and a Translation Memory eXchange (TMX) file is that a TBX file handles multiple languages, whereas a TMX file handles only two languages.
Note: Lingo supports TBX-Basic files (not the Full version).
In addition to importing a termbase from a TBX file, Lingo allows you to import a termbase from a CSV, XLS, or XLSX file. This feature is helpful if the person building or maintaining your termbase does not use Lingo.
Following are the basic steps for using a termbase in Lingo:
Important: Please note that some languages contain multiple dialects. Projects and TM databases must be mapped with the same language designations in order to be used together.
Note: When would you use a termbase, and when would you use TM? The two are related, but not the same thing. TM is used for quickly applying previously translated segments. Termbases are really an extra tool for making sure you are using the correct term in a translation (i.e., context). That's why termbases let you provide additional info about each term. Also, TM is necessary in order to use a termbase and apply its suggestions, but a termbase is not necessary in order to use TM.