FEATURE: Glossary management via Neos backend

[mficzel]

The backend module now allows to create glossaries for languages and to upload those to deepl. Only one glossary can be created for each source-target combination that is afterwards used automatically for translations between the specified languages.

This incorporates ideas from @lorenzulrich from #46 which in turn is based on https://github.com/robert-heinig/Sitegeist.LostInTranslation/tree/feature/glossaries. Thanks a lot for all this input.

Resolves: #5

• create glossary
• edit glossary items
• upload and use glossary
• add context to keep separate dictionaries between dev / stage / live environments
• find most recent dictionary via deepl api (source, target, environment)
• use deepl package from packagist https://packagist.org/packages/deeplcom/deepl-php
• refactor translationServiceTest for better readability

deepl api

[paavo]

Hey @mficzel
I just tested the Glossary Management Feature and i really like it 🤩

What im missing most, is a way, to use a global Glossary in multiple instances 🤔
Instead of sync glossary (upload local glossary) we maybe could split into a download/upload function?

This already would help a lot i guess 🤔
[] find most recent dictionary via deepl api

CSV-Import / Export also sounds like a nice feature 🤔

[mficzel]

FYI: I am working in #56 on refactoring and afterwards refinement of the glossary feature ... may take a bit but will alllow us to keep the code maintainable and use the official deepl php client behind the scene

[mficzel]

Close in favor of #63