Loading custom language files

[AleeeKoi]

Hello, I'm switching an existing project to laravel-lang.
The lang directory has some PHP files divided by context. So, the directory structure is like:

lang
    en
        validation.php
        common.php
        type.php
        ...
    it
        validation.php
        common.php
        type.php
        ...
   en.json
   it.json

Running the command php artisan lang:update everything is update, except for the .json (in the lang directory) that are not containing translations from custom php files (ex. common.php).

Is there a way to include them? Thanks

[andrey-helldar]

Hello! JSON files should be in the lang folder

lang
    en
        validation.php
        common.php
        type.php
        ...
    it
        validation.php
        common.php
        type.php
        ...
    en.json
    it.json

https://laravel.com/docs/11.x/localization#introduction

[andrey-helldar]

Just move them and rerun console command again:

mv en.json lang/en.json
mv it.json lang/it.json

php artisan lang:update

[AleeeKoi]

@

Hello! JSON files should be in the lang folder

Hi @andrey-helldar , sorry, the indentation was incorrect. I have updated it.
The two json file were altredy in the lang directory. Also, the are created correctly running php artisan lang:update.

What is missing in the json file generated, are the translations from custom php files (ex. common.php). Is there a way to include them?

[andrey-helldar]

Different files are not merged when the command is executed.

The only case when other content can be added to a file is when using a plugin.

For example: https://github.com/Laravel-Lang/translations-template/blob/main/src/Plugins/Foo.php#L18

What do you expect from executing the lang:update command?

[AleeeKoi]

What do you expect from executing the lang:update command?

I expect that all the php files are founded and included into the .json file, or using a custom config to indicate other languages files.

[andrey-helldar]

I got it. It won't work that way. Laravel doesn't work that way. Each translation file is an independent dataset.

BUT you can easily merge them by your own efforts by creating a console command. For example:

Artisan::command('lang:merge', function () {
    /** @var \DirectoryIterator $item */
    foreach (new DirectoryIterator(lang_path()) as $item) {
        if ($item->isDir() || $item->isDot()) {
            continue;
        }

        $target = json_decode(file_get_contents($item->getRealPath()), true);

        $locale = Str::before($item->getFilename(), '.');

        /** @var \DirectoryIterator $php */
        foreach (new DirectoryIterator(lang_path($locale)) as $php) {
            if ($php->isDir() || $php->isDot()) {
                continue;
            }

            $source = require $php->getRealPath();

            $target = array_merge($target, $source);
        }

        file_put_contents(
            lang_path($locale . '.json'),
            json_encode($target, JSON_UNESCAPED_SLASHES ^ JSON_UNESCAPED_UNICODE ^ JSON_PRETTY_PRINT)
        );
    }
});

But be aware that this will lead to problems with translations. It is correct to use them independently of each other.