anavel / translation

Manage laravel translation files from your admin panel

Anavel translation

Manage laravel translation files from your admin panel. This package depends on Anavel foundation

Features

• Easily manage app and vendor translation files.
• Automatically reorders translations (alphabetically)
• Easily create new language lines
• Arrays supported

Installation

Configuration

Publish translation config file with php artisan vendor:publish

Include the files you want to manage within the files array, like this:

    /*
    |--------------------------------------------------------------------------
    | Files to translate
    |--------------------------------------------------------------------------
    |
    */
    'files' => [
        'user'   => [
            'aFileName',
            'anotherFileName'
        ],
        'vendor' => [
            'vendorname' => 'vendorFileName'
        ]
    ],

user is an array of filenames (without extension) located in Laravel's default folder (resources/lang/LOCALE_NAME). vendor is an associative array of filenames (without extension), keyed by vendorname, located in Laravel's default folder (resources/lang/vendor/VENDORNAME/LOCALE_NAME).

This package will read and then write those files, so your app must have write permissions to those folders. You must specify a disc driver for Laravel to use:

config/anavel-translation.php:

    /*
    |--------------------------------------------------------------------------
    | File Disc Driver
    |--------------------------------------------------------------------------
    |
    | Disc driver pointing to resources/lang folder
    |
    */
    'filedriver'  => 'YOUR_DRIVER_NAME',

config/filesystem.php:

    'disks' => [
        [SOME OTHER FILE DRIVERS ],
        'YOUR_DRIVER_NAME' => [
            'driver' => 'local',
            'root'   => base_path('resources/lang'),
        ],
    ]

Versioning

If you use a versioning system (such as git) you should add the language folder to your gitignore. Otherwise, you might get conflicts if different users update the translations.

How it works

Translations reads the files that you specify in the config and displays their content in a form, tabbed by locale. The translation key becomes the input label and the translation itself becomes the input value. Locales are taken from the Anavel foundation config.

To make the translation process easier, Translation shows the same language entries in all locales, even if a key is missing in a given locale. In that case, the displayed text will be taken from the fallback locale (as Laravel does).

When saved, translations are written back to the files. If a file doesn't exist in a locale, a new one is created.

translation's Issues

Sobre os nomes deste sistema

Que nomes teñen as pezas deste framework? Como chegastes a eles?

(explicádenos como chegastes ata eles para que o entendamos mellor, please... se cadra ocórresenos algo tan wai, pero máis breve), 👯 / @cmoralesweb @ablunier

Arrays get overwritten

When adding elements, using the dot sintax (arraykey.key), if a previous array exists, it gets overwritten.

Support to add new language lines

Including arrays (for cases such as validation.php):

    /*
    |--------------------------------------------------------------------------
    | Custom Validation Attributes
    |--------------------------------------------------------------------------
    |
    | The following language lines are used to swap attribute place-holders
    | with something more reader friendly such as E-Mail Address instead
    | of "email". This simply helps us make messages a little cleaner.
    |
    */

    'attributes' => [],

Mandatory to define a file on 'user' key

If you only want to define vendor files to translate, you get an error of undefined offset

Multiple files for a vendor

When configuring files to translate for vendors:

/*
    |--------------------------------------------------------------------------
    | Files to translate
    |--------------------------------------------------------------------------
    |
    */
    'files' => [
        'vendor' => [
            'vendorname' => 'vendorFileName'
        ]
    ],

can't configure multiple 'vendorFileName'. It should accept multiple files (as array) for a vendor name.

Locale forms should be independent

Currently, all locales share the same form (and submit button). That means that missing entries get saved with the fallback locale if not edited.

Forms should be independent per tab, so only the visible locale gets submitted.

Remove translation line

Implement the possibility to remove a translation line (or array).