feat(translations): add DeepL translation management console commands #37
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add two new Artisan commands to automate translation workflows: - translations:manage - Main translation pipeline command that can extract translations from Laravel locale files and orchestrate the full translation process via DeepL API - translations:deepl - Low-level DeepL API wrapper providing direct translation services, language listing, usage monitoring, and API testing capabilities Key features: - Extracts translations from PHP locale files while preserving Laravel placeholders (:name) - Handles HTML tags by replacing them with placeholders to allow DeepL to translate text without markup - Supports batch processing to respect DeepL API limits and rate limiting - Generates properly formatted PHP locale files for target languages in specified instance - Supports both free and pro DeepL API endpoints This should make it easier to maintain translations across multiple instances and locales. If manually done, one would need to grab just the values from the locale arrays, remove placeholders and html tags, translate the orginal text, re-add placeholders and html tags, and then add the new locale array/files to the instance.
DeepL does not support Belgian variants so we will be disabling them to make things simpler. If we need to support them in the future, we will need to manually translate the content for fr-BE and nl-BE.
The `no` locale had some Dutch content which meant it was the `nl` locale. I further confirmed this by validating there was no `no` locale defined in the laravellocalization.php config file. Let's rename the folder to `nl`.
I ran translations:manage for all core locales: de, es, fr, it, and nl. The `ne` locale is for Nepali which is not supported by DeepL nor is it enabled in the laravellocalization.php config file. As such, we will be skipping it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This adds two new Artisan commands to automate translation workflows:
translations:manage- Main translation pipeline command that can extract translations fromLaravel locale files and orchestrate the full translation process via DeepL API
translations:deepl- Low-level DeepL API wrapper providing direct translation services,language listing, usage monitoring, and API testing capabilities
Key features:
specified instance
This should make it easier to maintain translations across multiple instances and locales. If manually done, one would need to grab just the values from the locale arrays, remove placeholders and html tags, translate the original text, re-add placeholders and html tags, and then add the new locale array/files to the instance.
CR Notes
I was originally going to just translate the
fixitcliniclocale files but it turned out that thebaselocale files were not fully translated. As such, we would have had a mix of translated and non-translated content on the website.To resolve this, and simplify future translations, I created these two new commands that would interact with the DeepL api and auto-translate the content for us.
qa_req 0