TYPO3 extension deepltranslate_glossary

	URL
Repository:	https://github.com/web-vision/deepltranslate-glossary
Read online:	https://docs.typo3.org/p/web-vision/deepltranslate-glossary/main/en-us/
TER:	https://extensions.typo3.org/extension/deepltranslate_glossary/
ISSUES:	https://github.com/web-vision/deepltranslate-glossary/issues/
RELEASES:	https://github.com/web-vision/deepltranslate-glossary/releases/

Description

This extension provides glossary-flavoured translations for the TYPO3 extension deepltranslate_core.

Compatibility

Branch	State	Composer Package Name	TYPO3 Extension Key	Version	TYPO3	PHP
main	development, active support	web-vision/deepltranslate-glossary	deepltranslate_glossary	^6, 6.0.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)

Features

• Extends EXT:deepltranslate_core as 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

Installation

Install with your favour:

• Composer
• TER / Extension Manager
• Git

We prefer composer installation:

composer require -W \
  'web-vision/deepltranslate-core':'~6.0.0@dev' \
  'web-vision/deepltranslate-glossary':'~6.0.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.

Sponsors

We very much appreciate the sponsorship of the developments and features in the DeepL Translate Extension for TYPO3.

DeepL Glossary feature sponsored by

• Universität Osnabrück
• Hochschule für Musik Würzburg
• Carl von Ossietzky Universität Oldenburg
• Friedrich-Ebert-Stiftung

Create a release (maintainers only)

Prerequisites:

• git binary
• ssh key allowed to push new branches to the repository
• GitHub command line tool gh installed and configured with user having permission to create pull requests.

Create release

Set RELEASE_BRANCH to branch release should happen, for example: 'main'. Set RELEASE_VERSION to 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 based on configuration' ; \
  RELEASE_BRANCH='main' ; \
  RELEASE_VERSION='6.0.0' ; \
  DEV_VERSION='6.0.1' ; \
  echo ">> Checkout branches" && \
  git checkout main && \
  git fetch --all && \
  git pull --rebase && \
  git checkout ${RELEASE_BRANCH} && \
  git pull --rebase && \
  echo ">> Create release ${RELEASE_VERSION}" && \
  git checkout -b release-${RELEASE_VERSION} && \
  sed -i "s/^COMPOSER_ROOT_VERSION.*/COMPOSER_ROOT_VERSION=\"${RELEASE_VERSION}\"/" Build/Scripts/runTests.sh && \
  sed -i "s/^  RELEASE_VERSION.*/  RELEASE_VERSION='${RELEASE_VERSION}' ; \\\\/" README.md && \
  sed -i "s/^  DEV_VERSION.*/  DEV_VERSION='${DEV_VERSION}' ; \\\\/" README.md && \
  tailor set-version ${RELEASE_VERSION} && \
  composer config "extra"."typo3/cms"."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}" && \
  sleep 10 && \
  gh pr checks --watch --interval 2 && \
  sleep 10 && \
  gh pr merge -rd --admin && \
  git remote prune origin && \
  git tag ${RELEASE_VERSION} && \
  git push origin ${RELEASE_VERSION} && \
  echo ">> Post-release - set dev version: ${DEV_VRESION}-dev" && \
  git checkout -b set-dev-version-${DEV_VERSION} && \
  sed -i "s/^COMPOSER_ROOT_VERSION.*/COMPOSER_ROOT_VERSION=\"${DEV_VERSION}-dev\"/" Build/Scripts/runTests.sh && \
  tailor set-version ${DEV_VERSION} && \
  composer config "extra"."typo3/cms"."version" "${DEV_VERSION}-dev" && \
  echo "${DEV_VERSION}-dev" > VERSION && \
  git add . && \
  git commit -m "[TASK] Set dev version ${DEV_VERSION}" && \
  git push --set-upstream origin set-dev-version-${DEV_VERSION} && \
  gh pr create --fill --base ${RELEASE_BRANCH} --title "[TASK] Set dev version \"${DEV_VERSION}-dev\"" && \
  sleep 10 && \
  gh pr checks --watch --interval 2 && \
  sleep 10 && \
  gh pr merge -rd --admin && \
  git remote prune origin

This 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.