hyva-themes / magento2-i18n-csv-diff
hyva-themes/magento2-i18n-csv-diff
Magento command to display all translations that are present in the first CSV file but not in the second.
Hyvä Themes - Magento translation CSV comparison command
hyva-themes/magento2-i18n-csv-diff
This module adds the bin/magento i18n:diff-csv and i18n:translate-csv commands.
i18n:diff-csv
The command takes two CSV files as arguments.
It displays all translations that are present in the first CSV file but not in the second.
i18n:translate
The command takes a target language 2-letter ISO code as the argument.
It reads a Magento localization CSV dictionary from stdin, translates it using the DeepL API, and writes it to stdout.
Be sure to check the automatic translations afterwards!
Usage Examples:
-
Collect all Magento and Hyvä strings:
bin/magento i18n:collect-phrases vendor/magento/ > magento-strings.csv bin/magento i18n:collect-phrases vendor/hyva-themes/magento2-default-theme/ > hyva-strings.csv bin/magento i18n:collect-phrases vendor/hyva-themes/magento2-theme-module/ >> hyva-strings.csv -
Find all Hyvä specific translations that are not part of native Magento:
bin/magento i18n:diff-csv hyva-strings.csv magento-strings.csv -
Find all translations that are missing in a Hyvä translation file:
bin/magento i18n:diff-csv hyva-strings.csv i18n/de_DE.csv -
Find all translations that are in a translation file but are not used in Hyvä:
bin/magento i18n:diff-csv i18n/de_DE.csv hyva-strings.csv -
Add new translations to an existing dictionary file.
bin/magento i18n:diff-csv hyva-strings.csv i18n/de_DE.csv | bin/magento i18n:translate-csv DE >> i18n/de_DE.csv
Installation
- Install via composer
composer require hyva-themes/magento2-i18n-csv-diff - Enable module
bin/magento setup:upgrade
Configuration
To use the Deepi18n:translate-csv command, configure your API key in the system configuration at Hyva Themes > Localization CLI > Translation > DeepL API Key.
License
The BSD-3-Clause License. Please see License File for more information.
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
Requires 1
| Package | Constraint |
|---|---|
| php | >=7.4.0 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from hyva-themes
View vendorTurn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.