Salix OS

pt_PT exists precisely so that there is no confusion between Portuguese and Brazilian Portuguese

But normally you just use pt for Portuguese and pt_BR for Brazilian Portuguese

Some examples:
https://l10n.gnome.org/teams/pt/
https://websvn.kde.org/trunk/l10n-kf5/
https://translations.launchpad.net/linu ... t/+lang/pt

@gapan I have already requested the Portuguese(pt) language for the rest of salix resources in Transifex (salixtools and salixtolls-gtk) in particular since dotnew and Salix resources already have the Portuguese(pt) language.

Although the translation is the same for both Portuguese pt and Portuguese (Portugal) pt_PT, we can keep both for now...

PS: In Slackel https://www.transifex.com/djemos/dashbo ... ojects/pt/ we are using Portuguese(pt) but in Slint https://crowdin.com/project/slint we are using Portuguese (Portugal)

Xfce desktop environment uses Portuguese(pt) https://www.transifex.com/xfce/dashboar ... ojects/pt/

Perhaps @DidierSpaier can help us decide

hugok wrote: ↑14. Feb 2022, 15:55 @gapan I have already requested the Portuguese(pt) language for the rest of salix resources in Transifex (salixtools and salixtolls-gtk) in particular since dotnew and Salix resources already have the Portuguese(pt) language.

Ah, just enabled them now. Thanks for the notification. I somehow missed the one transifex sent me.

hugok wrote: ↑14. Feb 2022, 15:55 Although the translation is the same for both Portuguese pt and Portuguese (Portugal) pt_PT, we can keep both for now...

PS: In Slackel https://www.transifex.com/djemos/dashbo ... ojects/pt/ we are using Portuguese(pt) but in Slint https://crowdin.com/project/slint we are using Portuguese (Portugal)

Xfce desktop environment uses Portuguese(pt) https://www.transifex.com/xfce/dashboar ... ojects/pt/

Perhaps @DidierSpaier can help us decide

Not really sure myself either.

Ok. In the meantime, I have already started the translation of Portuguese(pt).

For now both are Portuguese(pt and pt_PT) are translated. I just need to do a review, especially in https://www.transifex.com/gapan/salix/dashboard/

hugok wrote: ↑14. Feb 2022, 15:55 Perhaps @DidierSpaier can help us decide

Generally I suggest to use the languages_geographic area scheme. In the case of Portuguese if I am correct there a relatively huge differences between Portuguese as spoken in Portugal and Brazil. But I assume that in a technical field these differences are not major, so maybe that is not very important. If a translation doesn't exist in the locale pt_BR the fallback will be pt for gettext, so having it can help for this reason. But if there is a translation really in Brazilian Portuguese better tag it pt_BR.

As an aside a similar issue exists noticeably for Spanish. It can be handy to distinguish between es_ES and es_319 for instance as Spanish differ between Spain and Latin America, but less between countries of Latin America, but I digress.

As @DidierSpaier wrote, there are many differences between the Portuguese language spoken in Portugal and the one spoken in Brazil. One of the biggest problems and the one that led me to the translation, was finding the language code pt to be used and translating it into brazilian Portuguese. This is not correct as the only official language is Portuguese which of course is what is written and spoken in Portugal. The Brazilian Portuguese is only a variant due to the differences of the 2 countries but there are 8 countries/variants (if I am not mistaken) Angola, Brazil, Cape Verde, Guinea-Bissau, Macau, Mozambique, São Tomé e Príncipe and East Timor.

Just a quick explanation:
https://www.youtube.com/watch?v=SXitW0IDAjQ

Portuguese translations (pt and pt_PT) 100% translated

https://www.transifex.com/gapan/