Download the PHP package dive-be/laravel-lingo without Composer
On this page you can find all versions of the php package dive-be/laravel-lingo. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download dive-be/laravel-lingo
More information about dive-be/laravel-lingo
Files in dive-be/laravel-lingo
Package laravel-lingo
Short Description Import and export translations from CSV files
License MIT
Homepage https://github.com/dive-be/laravel-lingo
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-lingo
Laravel Lingo
⚠️ Minor releases of this package may cause breaking changes as it has no stable release yet.
What problem does this package solve?
Sometimes, clients will use translation services and supply CSV files with translations. You can use this package to import those translations.
Installation
You can install the package via composer:
This is the contents of the published config file:
Usage
A common usage is to load or export specific translations from a CSV file.
Example usage
Saving loaded translations to your local Laravel project
You can take the loaded translations and save them to your local Laravel project.
You may wish to load the existing translations from your Laravel app first, and then save (overwrite) the merged list of translations:
If you do not want to override translation keys that already exist (and only import new ones), you can configure this when parsing the file:
Exporting to a CSV file
Another common use case is exporting your translations to a CSV file, so you can send these to a client or translator.
Note: If you have keys for translations that only exist for a given language, you may wish to load all translations, and export for all languages. This way you can get the union of all translation keys across all those languages, along with the localized version. If translations are missing, those fields will be left empty.
This can easily be accomplished like this:
CSV file constraints (for importing translations)
- The CSV file must have headers corresponding to the different locales.
- The translation key's header must be
key. - By default, you must use a semicolon (
;) to separate columns. (You can modify the delimiter character.) - You cannot have duplicate column names (you may wish to rename empty columns after exporting from Excel or Numbers).
A valid file looks like this:
Testing
Changelog
Please see CHANGELOG for more information on what has changed recently.
Contributing
Please see CONTRIBUTING for details.
Security
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
Credits
- Nico Verbruggen
- All Contributors
License
The MIT License (MIT). Please see License File for more information.
All versions of laravel-lingo with dependencies
dive-be/php-crowbar Version ^1.0
illuminate/console Version ^9.0
illuminate/contracts Version ^9.0
illuminate/support Version ^9.0
league/csv Version ^9.8
symfony/var-exporter Version ^6.1