- What is pfcode/symfony-i18n-comparator and what problem does it solve?
- It is a Symfony utility that audits translation catalogs by comparing i18n resource files across locales. It surfaces missing keys, orphaned entries, and inconsistent values so localization gaps are caught before they reach production. It fits into console workflows and CI pipelines for continuous translation quality checks.
- How do I install pfcode/symfony-i18n-comparator in a Symfony project?
- Install it with Composer, typically as a development dependency: composer require --dev pfcode/symfony-i18n-comparator. Then check the repository README for any required registration or console command setup in your Symfony application. Because it is an auditing tool, keeping it in require-dev avoids adding it to production runtime dependencies.
- Which translation catalog formats does it support?
- The package supports multiple catalog formats, including YAML, XLIFF, and PHP translation files. That lets you compare projects that use Symfony's common translation resource types without converting files first. Review the README for any format-specific configuration or limitations.
- How does it find missing translation keys across locales?
- It compares your i18n resource files locale by locale and identifies keys present in one catalog but absent in another. The output is a readable diff that makes it easy to review gaps before release. You can run it manually during development or wire it into automated checks.
- What are orphaned translation entries and why do they matter?
- Orphaned entries are translation entries that are no longer used by the application or no longer referenced by your code. They add maintenance noise, can confuse translators, and may hide real localization gaps. The comparator flags these unused or orphaned entries so you can clean up catalogs.
- How does it handle inconsistent values for the same key in different locales?
- It compares values for the same key across catalogs and includes differences in the readable diff output. That helps you spot entries that may be out of sync or inconsistent so you can review them manually. It is an auditing aid, not an automatic translation correction tool.
- Can I use it in CI pipelines for automated translation checks?
- Yes, the tool is designed to fit into CI pipelines and console workflows for continuous translation quality checks. You can run the comparison command as a build step and review the diff output for missing or orphaned keys. Check the README for exit-code behavior and options if you want the build to fail on differences.
- Does it integrate with Symfony's translation component and which versions are supported?
- Yes, it integrates with Symfony's translation component and works with Symfony-style translation catalogs. For exact PHP and Symfony version constraints, check the package's composer.json and README, since support depends on the release. Use a Symfony version that is compatible with the translation component features the package relies on.
- Can I use pfcode/symfony-i18n-comparator in Laravel?
- It is built for Symfony's translation component and Symfony catalog workflows, so it is not a Laravel translation package. Laravel uses its own translation system, and this comparator does not document Laravel integration. Laravel teams would need a Laravel-specific translation checker or a custom comparison script.
- How does it compare to Symfony's built-in translation commands, and should it run in production?
- Symfony provides built-in commands such as debug:translation and lint:xliff that help inspect and validate translations, while this package focuses on cross-locale catalog comparison and readable diffs for missing, orphaned, and inconsistent entries. It is best used as a development or CI auditing tool, not in production request paths. Keep it in require-dev and run it where your translation resources are available.