Machine translation of missing keys

[andrey-helldar]

@caouecs, sorry for DDoS with PR :)

I thought it would be correct to create a separate PR for each localization. This will get rid of the noise of other people's files.

PS: to translate phrases, I relied on a script that receives a list of untranslated keys for the status.md page. Therefore, some nested keys, for example, "validation.php", were not translated.

Nevertheless, in my opinion, this is much better than nothing.

During processing, I requested the translation of only those keys that were not translated. I did not touch the keys that people translated.

Another problem I ran into was unsupported localization.

When requesting a translation, I pass the localization code in the ISO 639-1 format (service requirement), which does not contain some of the values. For example, fil. I took the names of localizations from ours up to the _ symbol.

I couldn't use Google Translate as they charge $40 per hour to access their API. The Yandex.Translate service completed the translation of all phrases in about 1.5 hours and charged $5.28.

Before:

After:

By the way, I also noticed that some words, for example, the names of countries, may coincide during translation - now the script does not fill in the exclusion files, so they are shown as untranslated.
I tried to run a script to fill in such fields, but I ran into a problem that really untranslated phrases also get into the exclusion files. Therefore, I did not fill in the exclusion files.

[caouecs]

Good, but I prefer to contact each referents or last people who worked on a language, just to have fixes ( if needed )

[andrey-helldar]

In principle, we can.

For example:

[andrey-helldar]

But not everywhere)

[caouecs]

Yes, because you have update the directory ;)

[andrey-helldar]

@caouecs, Hey! Sorry for not answering. At work, we are migrating the server and applications. I will be very busy for the next couple of days. As soon as I am free, I will do everything necessary according to my PR.

[caouecs]

No problem, I ask help to last translators, and the result is good ;)

[caouecs]

Translation of localizations is completed by 40%

[caouecs]

45%

[andrey-helldar]

It looks like spam from you, yes. But from the user's side these are 1-2 letters)

However, as far as I could see, until we started asking for help in translation, the developers were not interested in our project. But as soon as we contacted them personally, they immediately agreed to help.

¯_(ツ)_/¯

[caouecs]

I think they didn't know that we have a lot of updates on files

[andrey-helldar]

I think so too. It could also be that they stopped using our package.

[caouecs]

52%

[caouecs]

Yandex doesn't love Qatar ;)

[andrey-helldar]

I'll tell you more - he loves few people 😂

[caouecs]

We need to make a calendar with translations not reviewed, and a strategy to explain the reasons why the translations are not very very good.

[andrey-helldar]

Hmm...

[andrey-helldar]

See Laravel-Lang/lang#1713

Personally, I don't like the look of the emoji table.

But I have not yet figured out how to make it beautifully.

[caouecs]

https://laravel-lang.github.io/lang/status.html

I don't see all table on Safari and Firefox

[andrey-helldar]

Google Chrome too

Google Pages has a limited content width. Due to the addition of new characters, the width has become larger. I will reduce the number of displayed columns from 8 to 6.

[andrey-helldar]

Laravel-Lang/lang#1724

[caouecs]

I merge all without reviewer, and I indicate that it's possible to update translations after

[caouecs]

88% after accepted all machine translations and do some fixes

[dansleboby]

You should deepl.com free 500k and ther translation are way better!

[caouecs]

Yes, we know. When I find time, I will do a test ;)