web-vision/deepltranslate-glossary

This extension provides option to auto and renew translate within TYPO3 CMS

5.0.0 2024-12-20 13:56 UTC

Requires

• php: ^8.1 || ^8.2 || ^8.3 || ^8.4
• ext-curl: *
• ext-json: *
• typo3/cms-backend: ^12.4.2 || ^13.4
• typo3/cms-core: ^12.4.2 || ^13.4
• web-vision/deepltranslate-core: ^5.0.0 || ~5.0@dev

Requires (Dev)

• friendsofphp/php-cs-fixer: ^3.64
• php-mock/php-mock-phpunit: ^2.6
• phpstan/phpstan: ^1.10
• phpunit/phpunit: ^10.5
• ramsey/uuid: ^4.7
• saschaegerer/phpstan-typo3: ^1.9
• typo3/cms-belog: ^12.4.2 || ^13.4
• typo3/cms-install: ^12.4.2 || ^13.4
• typo3/cms-lowlevel: ^12.4.2 || ^13.4
• typo3/cms-rte-ckeditor: ^12.4.2 || ^13.4
• typo3/cms-scheduler: ^12.4.2 || ^13.4
• typo3/cms-setup: ^12.4.2 || ^13.4
• typo3/cms-tstemplate: ^12.4.2 || ^13.4
• typo3/cms-workspaces: ^12.4.2 || ^13.4
• typo3/testing-framework: ^8.2.7

Suggests

• typo3/cms-scheduler: Add the scheduler for automatic synchronizing glossaries

GPL-2.0-or-later

• web-vision GmbH
• Mark Houben
• Markus Hofmann
• Riad Zejnilagic Trumic
• Stefan Bürk

• extension
• translate
• TYPO3 CMS
• glossary
• deepl

README

TYPO3 extension deepltranslate_glossary

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

Features

• 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 web-vision/deepltranslate-glossary

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.

Prepare release locally

Set RELEASE_BRANCH to branch release should happen, for example: 'main'. Set RELEASE_VERSION to release version working on, for example: '5.0.0'.

echo '>> Prepare release pull-request' ; \
  RELEASE_BRANCH='main' ; \
  RELEASE_VERSION='5.0.1' ; \
  git checkout main && \
  git fetch --all && \
  git pull --rebase && \
  git checkout ${RELEASE_BRANCH} && \
  git pull --rebase && \
  git checkout -b prepare-release-${RELEASE_VERSION} && \
  composer require --dev "typo3/tailor" && \
  ./.Build/bin/tailor set-version ${RELEASE_VERSION} && \
  composer remove --dev "typo3/tailor" && \
  git add . && \
  git commit -m "[TASK] Prepare release ${RELEASE_VERSION}" && \
  git push --set-upstream origin prepare-release-${RELEASE_VERSION} && \
  gh pr create --fill-verbose --base ${RELEASE_BRANCH} --title "[TASK] Prepare release for ${RELEASE_VERSION} on ${RELEASE_BRANCH}" && \
  git checkout main && \
  git branch -D prepare-release-${RELEASE_VERSION}

Check pull-request and the pipeline run.

Merge approved pull-request and push version tag

Set RELEASE_PR_NUMBER with the pull-request number of the preparation pull-request. Set RELEASE_BRANCH to branch release should happen, for example: 'main' (same as in previous step). Set RELEASE_VERSION to release version working on, for example: 0.1.4 (same as in previous step).

RELEASE_BRANCH='main' ; \
RELEASE_VERSION='5.0.1' ; \
RELEASE_PR_NUMBER='123' ; \
  git checkout main && \
  git fetch --all && \
  git pull --rebase && \
  gh pr checkout ${RELEASE_PR_NUMBER} && \
  gh pr merge -rd ${RELEASE_PR_NUMBER} && \
  git tag ${RELEASE_VERSION} && \
  git push --tags

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.