What is best location to get locales / internationalization files?

[f1-outsourcing]

Where can I find the most up to date archive for localization files for magento? These[1] are quite old and not complete. Maybe create a repository for this on OpenMage, so they can be maintained here?

[1]
https://github.com/versedi/Magento-Locales

[luigifab]

Sadly, there are no other places. You can found elsewhere some translation packs.
I will think to PR a cleaned version of versedi/Magento-Locales, because it's a must have.

[f1-outsourcing]

Would be great to have it here. I am currently seeing quite a few weird translations so it is time to up date them.

[luigifab]

There are also https://crowdin.com/project/magento-1 and https://crowdin.com/project/magento-2.

[luigifab]

If I understand well, this is AFL/OSL v3: https://github.com/magento-l10n/language-fr_FR

[luigifab]

So we can get many recent translations. Yes?

[aterjung]

I would like to see a OM repo for language packs. For these language packs i know well, there is no more development done.
But i am not shure if https://github.com/versedi/Magento-Locales is a good source. It looks very outdated. Probably we should start from scratch and only add translations known to be good? Its impossible to check a translations quality if you don't speek the language.
At least, we should check the license for the language-packs.

[luigifab]

Yes, there are tons of mistakes from these translations (I have a script to fix CSV syntax and encoding). I using it, and have fixed some of them. I also mixed it from translations packs found elsewhere. From memory, there are 8000 strings to translate, and I prefer to start from existing translations.

From web archive, there are no license information:

Not sure how to found the information. Magento is dual licensed OSL/AFL v3, perhaps these translations use same licences. Perhaps we can ask at:

magento-lts/index.php

Line 13 in f99c9b0

* to [email protected] so we can send you a copy immediately.

[luigifab]

I remember that some CSV files from versedi/Magento-Locales are wrong (something like es_ES in de_DE).
Perhaps we can increase the percent for each locales by using open source languages packs from Magento 2 (not searched).

[addison74]

These translations are old and outdated in my opinion. Most likely many strings are missing from them. It would be ideal to start with the existing ones in OpenMage.

Speaking of translations, I remember meeting a developer who had concatenated all CSV translation files into one file named translate.csv. He had removed the duplicates and made the changes quickly. I have never considered this option because I am not in a similar situation, but maybe it would not be a bad idea at all.

[luigifab]

There are no translations in OpenMage, only en_US. In my previous comment I take all the CSV files from versedi/Magento-Locales, then I rebuild them by using en_US CSV files from OpenMage.

Final CSV are clean.

[luigifab]

Counts updated: https://github.com/luigifab/openmage-translations

[luigifab]

Yes, there are many work to do.

[f1-outsourcing]

Maybe it is good to have a different system for editing these locales instead of only working with csv files. Just for the purpose of having a better control of editing them. With gettext for instance you have some 'tools' to manage translations files.
Such a system should also take into account that one locale can have a different versions like a more casual and a more professional version, maybe also addressing.
Also maybe a little manual for when people add different strings to a theme or so, how they should work with translations, so these custom translations are not ending up in the repository.

[f1-outsourcing]

@luigifab

Yes, there are many work to do.

Can you create a repo so I can fork it and work on some translations?

[luigifab]

I created a repo.
I imported data from Magento2, riconeitzel and versedi.
Fully not tested and not checked.

[f1-outsourcing]

It looks like you currently left out 'key strings', if they do not have a value. I guess if you put a value of "" it will just blank the translation. But is this also when you do something like this:

Mage_Checkout.csv:"Checkout Method",

Because it would be handy if untranslated keys are already in these files, and you do not have to look them up. Unless there is some tool that can help with this?

[f1-outsourcing]

And would you like to have additions to these files at the end or first ordered like they are now?

[aterjung]

For German, the de-facto standard is: https://github.com/riconeitzel/German_LocalePack_de_DE Aren’t there similar projects for the other locales?

…

Am 08.01.2022 um 19:53 schrieb luigifab ***@***.***>:  Yes, there are many work to do. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.