Weave Code
Laravel Langman Laravel Package
liip/laravel-langman
Laravel Langman is a web-based translation manager for Laravel. Browse, edit, and organize language files, add new locales, and find missing translation keys from a clean admin interface—streamlining localization without touching files manually.
Language files manager in your artisan console. Semi-permanent fork until upstream becomes alive again
Frequently asked questions about Laravel Langman
- What is Laravel Langman and who is it for?
- Laravel Langman is a translation management tool for Laravel that provides a clean web interface for browsing and editing your application's language files. Instead of hand-editing PHP arrays or JSON files, you get a single screen listing every translation key and its value across all configured locales. It is aimed at developers and translators working in local development or content-editing workflows.
- How do I install liip/laravel-langman?
- Install it as a Composer dependency using the package name liip/laravel-langman. After that, follow the README for any service provider registration and configuration publishing steps, since these details can change between releases. Once installed, the translation editor is reachable through the routes the package registers.
- Which Laravel versions does Langman support?
- Laravel Langman supports both the legacy lang directory layout and the newer resources/lang structure, so it works across the Laravel versions that use either convention. Because Laravel's directory layout and PHP requirements shift between major releases, always check the package's composer.json constraints and README before upgrading Laravel. Pinning a compatible package version in composer.json is the safest approach.
- Does Langman work with both PHP array files and JSON translation files?
- Yes. Langman parses and writes both PHP array language files and JSON translation files, exposing their keys in the same interface. You can browse and edit either format without converting your project to a single style. This is useful for applications that use JSON files for front-end strings and PHP arrays for the rest.
- Does Langman scan both the lang and resources/lang directories?
- Yes, it scans your project's lang and resources/lang directories and exposes every translation key it finds. That means older projects using the root-level lang folder and newer projects using resources/lang are both covered. The scanned paths are configurable if your project keeps translations somewhere else.
- How do I find missing translation keys across all locales?
- Langman displays every key alongside its value for each configured locale, so any locale showing a blank or absent value is a missing translation. The built-in search and filter let you narrow the list down quickly rather than scrolling hundreds of entries. This makes it easy to audit outdated or missing strings before a release.
- Can I add a new locale from the Langman interface?
- Yes. Langman lets you add new locales and then edit translations for them directly in the interface. You should also make sure the locale is registered in your package configuration so it stays visible on subsequent visits. Adding a locale this way saves you from manually creating the corresponding language file or folder.
- Will editing a translation change the formatting or order of my language files?
- Langman is designed to preserve the structure and formatting of your language files when it saves changes. That said, it is still worth committing your lang files to version control before a bulk editing session so you can review the diff. Any unexpected reformatting is then easy to spot and revert.
- Is it safe to enable Langman in production?
- Langman is built for local development and content-editing workflows, not as a production-facing admin panel, so you should keep it disabled or access-restricted in production. Apply your usual middleware such as auth and authorization to its routes, or register it only in non-production environments. Exposing an unrestricted translation editor publicly would let anyone rewrite your application's strings.
- How do I configure which locales and file paths Langman displays?
- The package ships with a configuration file where you define the locale list and the translation paths to scan. Publish that config file and adjust the entries to match your project's structure and supported languages. Locales are read from your application's configuration, while paths can point at lang, resources/lang, or other custom directories.
Weaver
How can I help you explore Laravel packages today?