Glossary is a collection of term entries. An 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 Push button to indicate that term is used as a button caption. Translations in glossaries are considered to be high quality and carefully checked. This is why it is recommended to use them instead of your custom translations. Glossaries are used to make translations consistent.
Editable glossary is a database glossary where you can add new items, import items from termonology files, edit existing items and remove items. Soluling supports two kind of editable glossaries:
|Local database glossary||A database that contains glossary data in a Soluling glossary structure. Initially Soluling contains one empty local glossary.|
|Cloud glossary||A glossary that locates on a Soluling add-on product called Cloud Glossary. It implements same features as above local glossary but the actual glossary exists on cloud making it easily accessible to all users of your localization team no matter where they locate.|
In addition of editable glossaries you can also add read-only glossaries. Application supports 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.
Text file that contains terms. Regular expression is 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 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 editable glossary in a local SQLite database and adds that into Soluling's glossary list. The glossary is initially empty. You can import terminology data into the glossary from variouse sources.
You can have multiple local glossaries. In addition you have any number of cloud glossaries. However if you have several glossaries added into glossary list they might slow down the glossary engine. In that case it recommended to remove the read-only glossaries and import them into the editable glossary. Because local glossary works on database it can cope with very large term count.
If you want to maximize the glossary speed keep only the default local glossary and import all your existing glossaries into the local glossary. If you want to share the same terminology with multiple uses add a cloud glossary and import all your existing glossaries into the cloud glossary.
Soluling uses spell chechers for stemming that are needed when finding terms in your text.
What is the difference between a glossary, translation memory, existing translations, and machine translator?