Auto-update translations

[andrey-helldar]

We now have several problems:

1. Many localizations that no one translates (https://github.com/Laravel-Lang/lang/discussions/1389);
2. When creating new keys, you need to look for them in the "en" or "todo.md" file, copy-paste and translate.

I have an idea: what if I create functionality to track such changes and automatically make corrections?

For instance:

• added a new key to the file - the script will automatically insert this key into all localization files.
• the key is not translated in the localization file? - the script will send a request to Google Translate and save the translated value.

Yes, Google Translate doesn't always translate well, but it's better than nothing.

There are two problems we will face:

1. Comments will be removed from the files;
2. Google Translate only allows you to translate 500k characters per month for free. Roughly speaking, the current English language files contain 28,170 characters. In 76 localizations, this will be approximately 2'140'920 characters. Yes, only non-translated values will be sent for translation, but judging by the todo.md file, we have fully translated 3-7 localizations.

I have an idea how to do it quickly and easily.

@Laravel-Lang/laravel-lang, what do you think?

[andrey-helldar]

@Laravel-Lang/laravel-lang, guys?

[mohamedsabil83]

I talked about that before. I agree with auto insert the new keys to the localization files but without translations. It's enough to find the new keys in the localization files and translate them from English.

Also, we can use google translation for localizations that didn't have a translator yet.

[andrey-helldar]

@mohamedsabil83, I also came across this when I compared ru localization with en.

Okay, then I'll make the necessary changes one of these days.

[luisprmat]

In this moment I find it convenient to have an automated test suite with PHPUnit for todo.php script for testing the new features without damaging the previous ones and to be able to refactor with greater confidence.

[andrey-helldar]

Done! Laravel-Lang/lang#1560

[andrey-helldar]

@luisprmat, testing a translation is bad, because we know in advance that not all keys have been translated.

You can test the todo.md file for the ## <lang> line, but why? ..

The only thing I see good for testing is the key match in the files.

[andrey-helldar]

@luisprmat, i added tests: Laravel-Lang/lang#1560