Chapter 20. Using TaaS in OmegaT
Prev |  | Next

# Chapter 20. Using TaaS in OmegaT

## 1. Generalities

The TaaS service at https://demo.taas-project.eu/info provides terminology services in European languages (plus Russian). It allows accessing both public and private data, where private glossaries (called "collections") can be extracted from existing documents, and the target terms partly populated automatically from various sources.

## 2. Public and private collections

OmegaT allows accessing the public part of TaaS without any registration.

To access the private part, a user must create a key using https://demo.taas-project.eu/account/keys/create?system=omegaT.

The key must then be given to OmegaT using -Dtaas.user.key=xxxxx. OmegaT configuration launchers (OmegaT.l4J.ini, omegat.kaptn and OmegaT.sh) contain a template entry.

When accessing the service without a private key, the following message will be put in the log: TaaS API key not found. Go to https://demo.taas-project.eu/account/keys/create?system=omegaT to create your own key then give it to OmegaT with -Dtaas.user.key=xxxxx (TAAS_API_KEY_NOT_FOUND)

## 3. Accessing the TaaS service

Click on Options, Glossary to display the following options:

Browse TaaS Collections will allow browsing existing collections for the source and target languages of the project, and downloading them. Private collections are displayed in bold. The collections are downloaded as TBX glossaries in the current glossary folder.

TaaS Terminology Lookup: when checked, will allow querying TaaS data on a segment by segment basis. All collections (public and private) will be queried for the source and target language.

To limit the amount of data, it is possible to select a specific domain by selecting Select TaaS Terminology Lookup Domain. In that dialog, it's possible to select All domains or a specific one.

Prev |  | Next
Chapter 19. Glossaries | Home | Chapter 21. Machine Translation