Details
-
New Feature
-
Resolution: Fixed
-
None
-
Medium
-
Enable deepL language resources to use terminology as glossar.
-
Empty show more show less
Description
- DeepL allows now to upload terminology via API to be used for translations.
- A checkbox at the termCollections configuration decides, if the terminology of this termCollecton is automatically uploaded to DeepL.
- If yes for each language pair of DeepL that has a matching language combination in the termCollection AND that is assigned to the same client the terminology is uploaded
- It is then used together with that DeepL language resource, BUT ONLY if the DeepL language resource is used for a client, that belongs to both: the DeepL language resource and the TermCollection.
- If the checkbox is unchecked in the TermCollection OR the client is removed from the TermCollection or the DeepL language resource OR one of both language resources is deleted, the terminology on the side of DeepL is deleted.
- If the checkbox is checked in a termCollection and for the same language combination in another termCollection the checkbox is already checked and that other termCollection belongs to at least one of the same clients, then a pop-up appears:
- EN: Heading: "Unassign DeepL glossary source" for other TermCollection? For one or more of the clients assigned to your current TermCollection the TermCollection XYZ has already been assigned as "DeepL glossary source". Should the TermCollection XYZ be unassigned as glossary source for all of its assigned clients?
- DE: Überschrift: Zuweisung "DeepL Glossar Quelle" für andere TermCollection entfernen? Für einen oder mehrere Kunden, die Ihrer aktuellen TermSammlung zugeordnet sind, wurde die TermSammlung XYZ bereits als "DeepL glossary source" zugewiesen. Soll die Zuweisung der TermKollektion XYZ als Glossarquelle für alle ihr zugewiesenen Kunden aufgehoben werden?
- The same check as outlined in the bullet before must also be done, if the checkbox "DeepL glossary source" is checked AND a new client is added to the language resource AND this client is already to another TermCollection that is marked as DeepL glosssary source.
- administrativeStatus (called "Usage status" in TermPortal) must be taken into account, when sending terminology to DeepL
- The relevant value on DB-level, that needs to be checked is the status column in the terms_term table
- If it has the value deprecatedTerm, the term must not be send to DeepL
- Since only one source and one target alternative can be send to DeepL for each source term:
- If the source term has multiple target alternatives in the target language, the one that has the status value preferredTerm must be send to DeepL
- If there are multiple target terms with the value preferredTerm, then the first one should be used
- If there is no target term with preferredTerm, but multiple with admittedTerm, then the first one of those should be used
- If there are multiple source terms with exactly the same string, the one of the first termEntry should be send to DeepL
- The DeepL terminology api functionality is documented here https://www.deepl.com/docs-api/managing-glossaries/
- syncing the term collection to DeepL should be done in cron job where the time to do this is configured
- according to the DeepL api we are not able to update Glossary, on each sync we delete the Glossary and create new one with updated content
- on each term collection upload/update sync with DeepL
Attachments
Issue Links
- mentioned in
-
Page Loading...