PHPackages                             sluy/laravel-translation - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Localization & i18n](/categories/localization)
4. /
5. sluy/laravel-translation

ActiveLibrary[Localization & i18n](/categories/localization)

sluy/laravel-translation
========================

Manage your translation in the correct way with Laravel. Export and import to another formats, do things in most used frontend Frameworks and more!.

01PHPCI failing

Since Feb 8Pushed 6y ago1 watchersCompare

[ Source](https://github.com/sluy/laravel-translation)[ Packagist](https://packagist.org/packages/sluy/laravel-translation)[ RSS](/packages/sluy-laravel-translation/feed)WikiDiscussions master Synced 3d ago

READMEChangelogDependenciesVersions (1)Used By (0)

Laravel Translations
====================

[](#laravel-translations)

Store your translation files in different formats (database, json, js, xml, php ) with a single command.

We know it, Laravel is very powerfull and the titan in Php Frameworks; however, some consistence in it is very squishy, for example, Translations.

You have a single files for translations and you can edit it simply and faster, but... When you make a SPA ? Vue app? Where stay a robust interface to manage translations? This is the start of the problem.

We create an easy commands to manipulate translations in different formats and generated a simple class (Vanilla JS and Vue.js at the moment) to load it in frontend apps.

Thats is all, format conversions and single functions to translate in front, who needs more with Laravel?

Another "db translations" for Laravel?
--------------------------------------

[](#another-db-translations-for-laravel)

No, never.

Some libraries (well, the vast majority) offers to you a bridge to use Db in Translations (in some cases it will replaces Laravel translation) + any loader + some things and bumb: another db translations library.

We offers next level of "comfort" : Manage all the translations of you need and enjoy all the "things" to do with that.

Installation
------------

[](#installation)

You can install the package via composer:

```
composer require sluy/laravel-translation
```

You could publish migrations, configuration and translations for views with:

```
php artisan vendor:publish --provider="Sluy\LaravelTranslation\LaravelTranslationServiceProvider"
```

Configuration
-------------

[](#configuration)

With some configurations (or none in many cases) you can perform all package functions:

```
//config/laravel-translation.php