- What is oguzhanbukcuoglu/laravel-translation used for?
- It is a Laravel package for managing application translations through a database-backed interface. You can scan a project for translation keys, edit strings for multiple locales, and sync or export PHP language files. It is aimed at teams that want a managed workflow instead of manually maintaining lang files.
- How do I install laravel-translation in a Laravel project?
- Install it with Composer using the package name oguzhanbukcuoglu/laravel-translation, then follow the package README for setup. Because translations are database-backed, you will typically need to publish any package configuration and run its migrations before scanning or editing strings. Check the README for the exact service provider and publishing steps required for your Laravel version.
- Does this package support multiple locales?
- Yes, the package is designed for editing translation strings across multiple locales. You can manage the same keys for different languages through the database-backed interface. This helps keep locale coverage consistent when new keys are added.
- How does the translation key scanner work?
- The scanner looks through your Laravel project for translation keys used in code and views. Those keys can then be managed in the package interface, making it easier to spot missing or unused translations. This reduces the need to manually grep for every __() or @lang call.
- Can I export translations to Laravel PHP language files?
- Yes, the package supports syncing or exporting translations into PHP language files. That means you can use the database interface for editing while still producing standard Laravel lang files. It is useful when you want version-controlled language files in your deployment.
- Which Laravel versions does this package support?
- The provided package overview does not list specific Laravel version constraints. Check the composer.json file or the package page on Packagist for the supported PHP and Laravel versions. Confirm compatibility before adding it to an existing application.
- Is it safe to use database-backed translations in production?
- It can be used in production, but database reads for translations may add overhead compared with plain PHP language files. A common approach is to edit translations in the interface and then sync or export PHP files for runtime use. Review caching, migration, and deployment steps before rolling it out.
- How does this compare to editing Laravel lang files manually?
- Manual editing means maintaining nested PHP arrays by hand for every locale. This package adds a database-backed interface, key scanning, multi-locale editing, and sync or export to PHP files. It is a better fit for teams that want a managed translation workflow while still being able to output standard Laravel language files.
- Can I test or preview translations before deploying?
- You can review and edit strings per locale in the database-backed interface before syncing or exporting them. After exporting, run your Laravel test suite to confirm that keys resolve as expected in each locale. This helps catch missing translations before they reach production.
- How do I keep translations in sync after deployment?
- Use the package's sync or export features to write translations back to PHP language files, then include those files in your release process. This keeps runtime translation loading aligned with the language files you deploy. It also lets you keep translations under version control if that is part of your workflow.