This extension provides glossary-flavoured translations for the TYPO3 extension deepltranslate_core.
| Branch | State | Composer Package Name | TYPO3 Extension Key | Version | TYPO3 | PHP |
|---|---|---|---|---|---|---|
| main | development, active support | web-vision/deepltranslate-glossary | deepltranslate_glossary | ^6, 6.1.x-dev | v13 + v14 | 8.2, 8.3, 8.4, 8.5 (depending on TYPO3) |
| 5 | active support | web-vision/deepltranslate-glossary | deepltranslate_glossary | ^5, 5.1.x-dev | v12 + v13 | 8.1, 8.2, 8.3, 8.4, 8.5 (depending on TYPO3) |
- Extends
EXT:deepltranslate_coreas public available addon. - TYPO3-conform database records for own glossaries
- Synchronize button in glossary module folders
- Managing for glossaries by CLI
- Cleanups and auto-updates by CLI scripts or scheduler tasks
Install with your favour:
We prefer composer installation:
composer require -W \
'web-vision/deepltranslate-core':'~6.1.0@dev' \
'web-vision/deepltranslate-glossary':'~6.1.0@dev'Note
Be aware that EXT:deepltranslate_glossary is a public addon for the
EXT:deepltranslate_core extension and cannot be used standalone,
and requires having EXT:deepltranslate_core DeepL API key set and site
configuration set according to the EXT:deepltranslate_core documentation.
We very much appreciate the sponsorship of the developments and features in the DeepL Translate Extension for TYPO3.
- Universität Osnabrück
- Hochschule für Musik Würzburg
- Carl von Ossietzky Universität Oldenburg
- Friedrich-Ebert-Stiftung
Prerequisites:
- git binary
- ssh key allowed to push new branches to the repository
- GitHub command line tool
ghinstalled and configured with user having permission to create pull requests.
Create release
Set
RELEASE_BRANCHto branch release should happen, for example: 'main'. SetRELEASE_VERSIONto release version working on, for example: '5.0.0'.
Important
Requires GitHub cli tool with personal token and
maintainer permission on the extension repository.
echo '>> Create release' ; \
RELEASE_BRANCH='main' ; \
RELEASE_VERSION='6.0.2' ; \
NEXT_DEV_VERSION='6.0.3' ; \
git checkout main && \
git fetch --all && \
git pull --rebase && \
git checkout ${RELEASE_BRANCH} && \
git pull --rebase && \
git checkout -b release-${RELEASE_VERSION} && \
sed -i "s/^COMPOSER_ROOT_VERSION.*/COMPOSER_ROOT_VERSION=\"${RELEASE_VERSION}\"/" Build/Scripts/runTests.sh && \
tailor set-version ${RELEASE_VERSION} && \
echo "${RELEASE_VERSION}" > VERSION && \
git add . && \
git commit -m "[RELEASE] ${RELEASE_VERSION}" && \
git push --set-upstream origin release-${RELEASE_VERSION} && \
gh pr create --fill --base ${RELEASE_BRANCH} --title "[RELEASE] ${RELEASE_VERSION}" && \
gh pr view --web && \
sleep 30 && \
gh pr checks --watch --interval 2 && \
sleep 5 && \
gh pr merge -rd --admin && \
git remote prune origin && \
git tag ${RELEASE_VERSION} && \
git push --tags && \
git checkout -b set-dev-version-${NEXT_DEV_VERSION} && \
tailor set-version ${NEXT_DEV_VERSION} && \
echo "${NEXT_DEV_VERSION}-dev" > VERSION && \
sed -i "s/^COMPOSER_ROOT_VERSION.*/COMPOSER_ROOT_VERSION=\"${NEXT_DEV_VERSION}-dev\"/" Build/Scripts/runTests.sh && \
sed -i "s/^ RELEASE_VERSION=.*/ RELEASE_VERSION='${RELEASE_VERSION}' ; \\\/" README.md && \
sed -i "s/^ NEXT_DEV_VERSION=.*/ NEXT_DEV_VERSION='${NEXT_DEV_VERSION}' ; \\\/" README.md && \
git add . && \
git commit -m "[TASK] Set \"${NEXT_DEV_VERSION}-dev\"" && \
git push --set-upstream origin set-dev-version-${NEXT_DEV_VERSION} && \
gh pr create --fill --base ${RELEASE_BRANCH} --title "[TASK] Set \"${NEXT_DEV_VERSION}-dev\"" && \
gh pr view --web && \
sleep 30 && \
gh pr checks --watch --interval 2 && \
sleep 5 && \
gh pr merge -rd --admin && \
git remote prune originThis triggers the on push tags workflow (publish.yml) which creates the upload package,
creates the GitHub release and also uploads the release to the TYPO3 Extension Repository.
| Version | Supported | End of Support |
|---|---|---|
| 6.x | ✅ | 2029-06-30 |
| 5.x | ✅ | 2027-12-31 |
Found a vulnerability? Please report it privately via our security report form — do not open a public issue. See SECURITY.md for the full vulnerability disclosure policy, including what to expect and our safe harbor statement.
Hereby, web-vision GmbH declares that the product with digital elements type DeepL Translate: Glossary is in compliance with Regulation (EU) 2024/2847.
The full text of the EU declaration of conformity is available at the following internet address: https://security.web-vision.de/conformity/web-vision/deepltranslate-glossary/6.1.0/en/
The full declarations are also included in this repository: English · Deutsch.
This extension is released under the GPL-2.0-or-later license.