- Does olek-php/auto-translator-bundle work with Laravel?
- No. Auto Translator Bundle is built as a Symfony bundle, so it registers through Symfony's kernel and configuration system rather than a Laravel service provider. Laravel applications can still borrow its approach, but you would need a bridge package or a Laravel-specific translation automation tool. If your project is Laravel, evaluate it as a reference implementation rather than a drop-in dependency.
- How do I install auto-translator-bundle with Composer?
- Install it with Composer using the package name olek-php/auto-translator-bundle. Because it is a Symfony bundle, you then enable it in your bundle registration and publish or create its configuration file. Check the repository README for the exact bundle class name and any required environment variables for provider credentials before running any console commands.
- Which translation providers does the bundle support?
- The bundle ships with DeepL and Google providers and also allows custom providers. You select the provider through configuration, so switching services does not require changing your locale files. A custom provider is the right option when you need an internal glossary, a self-hosted model, or an API the bundle does not cover out of the box.
- How does it detect missing or outdated translation keys?
- It scans your locale files and compares keys across all configured locales. Keys that exist in one locale but not another are treated as missing, and keys whose source string changed are treated as outdated. That means the bundle needs a reference locale to diff against, so keep one locale complete and canonical.
- Will it overwrite my existing translations or break placeholders?
- The bundle is designed to preserve existing translations and placeholders, so it fills gaps rather than rewriting everything. Placeholders are carried through to the translated string, which matters for parameters like %name% or :count. Always run it on a clean branch first so you can review the diff before committing.
- How do I configure locale and domain filtering?
- Locales and translation domains are configurable, letting you limit a run to specific languages or specific message domains. This is useful on large projects where translating everything at once would be slow or costly. Start with a single domain and locale pair to validate output quality before widening the scope.
- What console commands are available for batch and incremental runs?
- The bundle provides console commands for both full batch translation and incremental runs that only touch missing or outdated keys. Incremental runs are the practical choice for CI or scheduled jobs because they keep API usage low. Batch runs are better when onboarding a new locale from scratch.
- Which Symfony and PHP versions are supported?
- Support depends on the constraints declared in the package's composer.json, so check that file or the Packagist page before upgrading. Symfony bundles often lag behind the newest major release, so verify your Symfony version is inside the allowed range. If you are on an older Symfony LTS, confirm the bundle still receives updates for it.
- How should I test automated translations before using them in production?
- Run the commands against a staging copy of your translation files and review the diff for tone and placeholder handling. Machine translation quality varies by domain, so spot-check long strings, UI labels, and anything legally sensitive. Keeping the generated files under version control makes rollback and review straightforward.
- What are the alternatives to auto-translator-bundle for PHP projects?
- Alternatives include Laravel-focused translation managers, standalone translation management platforms, and custom scripts that call DeepL or Google directly. The main trade-off is integration depth versus portability: a Symfony bundle fits Symfony cleanly, while a SaaS platform works across frameworks. Choose based on whether you want automated catalog syncing inside your repo or an external translation workflow.