PHPackages khalyomede/laravel-translate - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Localization & i18n](/categories/localization) 4. / 5. khalyomede/laravel-translate ActiveLibrary[Localization & i18n](/categories/localization) khalyomede/laravel-translate ============================ Translate missing keys in JSON file, CI friendly. 0.4.0(2y ago)1322[4 issues](https://github.com/khalyomede/laravel-translate/issues)MITPHPPHP >=8.2.0 Since Mar 25Pushed 2y ago1 watchersCompare [ Source](https://github.com/khalyomede/laravel-translate)[ Packagist](https://packagist.org/packages/khalyomede/laravel-translate)[ RSS](/packages/khalyomede-laravel-translate/feed)WikiDiscussions master Synced 1mo ago READMEChangelogDependencies (8)Versions (7)Used By (0) Laravel Translate ================= [](#laravel-translate) Translate missing keys in JSON file, CI friendly. Summary ------- [](#summary) - [About](#about) - [Features](#features) - [Prerequisites](#prerequisites) - [Installation](#installation) - [Examples](#examples) - [Tests](#tests) About ----- [](#about) I have a web app and I always find myself pushing code where I added a new translation key that I forgot to translate in other of my supported languages. I also often forget to add my "static" model field that I should translate (which are most of the time linked to reference tables). I create this package to help me find out which keys I missed to translate before pushing and deploying in production. I use it on my CI as well in case I forget to run the check locally. Features -------- [](#features) - Can add missing translation by parsing on Blade and PHP files (supports `__()`, `trans()`, `trans_choice()`, `@lang()` and `@choice()` functions) - Can use a `--dry-run` option to only check for missing keys (and returns a **non zero code**, useful to put in a CI) - Can sort translated keys - can remove unused keys - Can translate Models's column values Prerequisites ------------- [](#prerequisites) This package assumes you heavily rely on JSON files instead of PHP files to store your translations. It will pull all non [short-keys](https://laravel.com/docs/10.x/localization#using-short-keys) translations (like `validation.required`, `home.headline`, ...) and put them in your "lang/\[lang\].json` file. I also advice to use plain English as your translation key, for various reasons: - Your files are more understandable using `__("You must subscribe to the premium plan to use this feature.")` instead of `__("plan.subscribe.warn_message")` - You don't spend minutes trying to figure out the best short key name to represent the text, you just use the text as the key - You can easily pass the "\[lang\].json" file to a company (or a third-party service) to translate the keys in the lang of your choice - If you have no countable translations, you can omit to configure the "en" translation since your keys are exactly your English translation (Laravel prints the key if the lang file is not found) Installation ------------ [](#installation) Install the package: ``` composer require --dev khalyomede/laravel-translate ``` Publish the configuration file: ``` php artisan vendor:publish --tag "translate" ``` Examples -------- [](#examples) - [1. Check for missing translations](#1-check-for-missing-translations) - [2. Add missing translations](#2-add-missing-translations) - [3. Customize which folders to parse](#3-customize-which-folders-to-parse) - [4. Remove translation keys not found](#4-remove-translation-keys-not-found) - [5. Translate models data](#5-translate-models-data) - [6. Add raw array of keys](#6-add-raw-array-of-keys) - [7. Ignore keys](#7-ignore-keys) ### 1. Check for missing translations [](#1-check-for-missing-translations) Call the command using `--dry-run` to only check for missing keys without writing the missing keys. ``` php artisan translate --dry-run ``` You can add more langs by editing the `config/translate.php` file. ``` return [ "langs" => [ "fr", "en", "pt", ], // ... ]; ``` ### 2. Add missing translations [](#2-add-missing-translations) Call the command without flags to actually write the missing keys. ``` php artisan translate ``` You can add more langs by editing the `config/translate.php` file. ``` return [ "langs" => [ "fr", "en", "pt", ], // ... ]; ``` ### 3. Customize which folders to parse [](#3-customize-which-folders-to-parse) By default, the folders "app" and "resources/views" are the only that are parsed. If you need to add more, just change the folders in the config file at "config/translate.php". ``` return [ // ... "include" => [ "app", "resources/views", ], // ... ]; ``` This will instruct the command to find every files ending with `.php` or `.blade.php` in the folders (by searching recursively). ### 4. Remove translation keys not found [](#4-remove-translation-keys-not-found) If you are sure all the keys are "findable" by the command in your code, you can enable a configuration to automatically remove keys that are not found. Head to the configuration file at "config/translate.php". ``` return [ "remove_missing_keys" => true, // ... ]; ``` ### 5. Translate models data [](#5-translate-models-data) When you use any translation function to display the translated text of a model column, and this model appears to be a statically seeded table that will not be changed otherwise, you might want to pull all texts from the desired column to be translated. Using `translate.models` config key, you can do it. Head to "config/translate.php": ``` use App\Models\UserType; return [ // ... "models" => [ UserType::class => "name", ], // ... ]; ``` If you have multiple columns for the same model, you can also pass an array: ``` use App\Models\Post; return [ // ... "models" => [ Post::class => [ "title", "description", ], ], // ... ]; ``` You pass it the name of the model as key, and the name of the column to pull translation from as the value. This assumes you translate your model like this for example: ``` @php $userTypes = App\Models\UserType::all(); @endphp All @foreach ($userTypes as $userType)