Translations

Google Translate
DeepL

Under Administration → Settings in the translations settings tab the settings regarding translation setup can be changed. Translation handling is implemented different places – e.g. in Perfion Web client grid and Perfion Windows client grid, please see relevant user guides:

Web Client: Managing item data - Google or DeepL translations
Windows Client: Translate
Action: Perfion.Translate()

By default translation handling is disabled:

By choosing the Translation Service in the Active Service drop-down, entering a valid API key relevant for the selected service is enabled.

Google Translate

Google Translate API key can be obtained from Google, please use documentation from Google, starting point: https://cloud.google.com/translate/docs/setup

Google Translation enabled:

DeepL

DeepL API key can be obtained from DeepL, please use documentation from DeepL, starting point: https://www.deepl.com/pro-api?cta=header-pro-api

With DeepL there is the possibility to choose between a Free API and Pro API account. The differences between the two accounts are presented also in the link above.

Another DeepL specific functionality is using glossaries. With glossaries you can manage how DeepL should translate specific words or word combinations. For instance industry, company or international terms, brands or names can have specific custom translations.

Creating a glossary is done by clicking on the Create button. The following overlay will open:

Glossary type

There are two options how to make your glossary:

Tabular-separated (TSV) - use a Tab to separate the source value and target value
Comma-separated (CSV) - use a comma to separate the source value and target value

Glossary name

The name of the glossary that will be visible in the Translations settings screen under “Glossary”.

Source/Target language

The source language is the language you translate from and the target language is the language you translate to. DeepL language codes need to be used, so not the Perfion language codes!

Please check the DeepL website for the most current list with source and target language codes: DeepL Language Codes

It will support one glossary per language combination.

Glossary

In this part the actual glossary can be constructed. Depending on the glossary type, the source and target language values are separated with a Tab (TSV) or a comma (CSV).

Examples inputs could be for a EN (English) → NL (Dutch) language combination:

Sage,Sage → the brand “Sage” should not be translated, sage is also a herb.

state-of-the-art,state-of-the-art → if a text uses this word combination, it should not be translated.

brew,brouwen → DeepL transaltes brew by default to “zetten” in Dutch, but the more professional term “brouwen” is required.

Clicking on OK will add the glossary for this language combination.

As Perfion 2025-R3 was developed, DeepL did not supported editing glossaries through API, only deleting and creating glossaries. Perfion “edits” glossaries by creating a copy of the existing glossary, creating a new with the changes made by user and then deleting the old one.
DeepL has since released support for real editing. Perfion supported this is planned for 2026-R1