search

Jguer / yay

Yet another Yogurt - An AUR Helper written in Go
GNU General Public License v3.0
10.61k stars 349 forks source link

Maintaining the French and French (France) translations #2417

Open HarmfulBreeze opened 3 months ago

HarmfulBreeze commented 3 months ago

Hi!

I've noticed you were looking for translation reviewers and language coordinators. I'd like to apply for the latter. I've been using yay for quite some time and I would like to give back to the community some of the time I've saved using yay.

For reference, I've been working on various community and proprietary projects and trying to deliver professional-grade translations. Projects include Waze, the PCSX2 emulator, Android launcher Lawnchair, and others.

I've joined both Transifex teams and noticed that fr is quite far behind fr_FR. Do they both really need to exist? Shouldn't it just be fr until some people are interested in translating the app in their local dialect?

Do you also have a stance on fixing translation bugs? I usually prefer to fix a bug in the translated string, then open an issue/submit a PR to fix it in the source string. But I'm also fine with waiting on the source fix being merged.

Thanks! Pierre

Jguer commented 3 months ago

I've joined both Transifex teams and noticed that fr is quite far behind fr_FR. Do they both really need to exist? Shouldn't it just be fr until some people are interested in translating the app in their local dialect?

I've just enabled the option to automatically populate from dialect to general. I think this comes from legacy. the fr_FR have existed longer than the fr translations.

Do you also have a stance on fixing translation bugs? I usually prefer to fix a bug in the translated string, then open an issue/submit a PR to fix it in the source string. But I'm also fine with waiting on the source fix being merged.

Normally, if there's an issue with the source string, fix that in the code base (and later in transifex)

I need to automate the generation of the .po file for transifex (it follows the en.po of the repo), but it's not been so simple

HarmfulBreeze commented 3 months ago

Looks good to me, and thank you for the rights!

I'd love to try and help you with the PO file generation. Hopefully I manage to find some time.

Jguer commented 3 months ago

Normally I extract the .po using xgotext 

go install github.com/leonelquinteros/gotext/cli/xgotext@latest
xgotext -v -in ./ -out ./po
mv po/default.pot po/en.po
HarmfulBreeze commented 2 months ago

I have reviewed all translations for both fr and fr_FR, except one. I think I need an example usage of the "None" string, in order to use the proper gender. (I can also use "Aucun(e)" which is the neutral equivalent, but I'd rather use the correct gender in the first place.) Could you give me such an example?

Normally I extract the .po using xgotext

go install github.com/leonelquinteros/gotext/cli/xgotext@latest
xgotext -v -in ./ -out ./po
mv po/default.pot po/en.po

Perhaps this could be automated with GitHub Actions? :)

HarmfulBreeze commented 1 month ago

About the "None" string, I decided to use Pacman's translation ("--") for consistency's sake. I also believe this issue can be closed.