We discovered that glossaries only work if the ID is added in typoscript (like described in https://docs.typo3.org/p/dmitryd/dd-deepl/12.7/en-us/Configuration/TypoScriptReference/Setup.html).
The solution works fine, but makes it very uncomfortable to "edit" glossaries. As deepl allows no editing of glossaries, every "editing" means to remove the existing glossary and upload a new one. This leads to an new ID which then forces you to edit the typoscript.
While editing glossaries is a task that every editor should be able to do, editing typoscript is definitly not.
So in the current state there is no effective way for editors to update glossaries.
Deepl suggest to use the name as identifier for "editing" glossaries (https://developers.deepl.com/docs/api-reference/glossaries). Could this also be an option here? Would be nice if you could also use the name as an identifier, as it can stay the same after every upload.
We discovered that glossaries only work if the ID is added in typoscript (like described in https://docs.typo3.org/p/dmitryd/dd-deepl/12.7/en-us/Configuration/TypoScriptReference/Setup.html).
The solution works fine, but makes it very uncomfortable to "edit" glossaries. As deepl allows no editing of glossaries, every "editing" means to remove the existing glossary and upload a new one. This leads to an new ID which then forces you to edit the typoscript.
While editing glossaries is a task that every editor should be able to do, editing typoscript is definitly not.
So in the current state there is no effective way for editors to update glossaries.
Deepl suggest to use the name as identifier for "editing" glossaries (https://developers.deepl.com/docs/api-reference/glossaries). Could this also be an option here? Would be nice if you could also use the name as an identifier, as it can stay the same after every upload.