Added pt_PT Readme

[qlpqlp]

Added pt_PT Readme

[edtubbs]

I wish I could review these but I can't read Portuguese. I'll try to find another way to help with it though.

[qlpqlp]

eheh, only saw this today. Intense last days for me :P
I will try to again ask any Portuguese reviewers :D

[patricklodder]

Before we spend a lot of time on reviews, what's the benefit of having both pt-PT and pt-BR?

Can we choose one that everyone understands?

[qlpqlp]

Before we spend a lot of time on reviews, what's the benefit of having both pt-PT and pt-BR?

Can we choose one that everyone understands?

In a cultural way, some people don't like to read in Brazilian (pt-BR) and others don't like to read Portuguese in (pt_PT)
It´s ~ like you people listen Canadian people speak vs American people speaking, but the writing and words in Portuguese and Brazilian are completely different, but

Example:

User: Usuário (pt-BR)
User: Utilizador (pt-PT)

Password: Senha (pt-BR)
Password: Palavra-passe (pt-PT)

A greater explanation is in this website : https://www.dicio.com.br/portugues-de-portugal-e-a-diferenca-com-o-portugues-do-brasil/

[patricklodder]

I'm sure it's relevant in the context of ice cream, hospitals and sandwiches, but what about Dogecoin Core. Is the current pt-BR translation such an atrocity to a large amount of people that don't speak English and only speak pt-PT, that this is needed?

I'm okay with doing this inside the software translation, because that is something you see every time you use the software. The README on the other hand is something you won't read often and I am worried to set a precedent and ending up with dozens of readme translations that trail any change with a huge time gap and therefore become an obstacle to timely information.

[qlpqlp]

I'm sure it's relevant in the context of ice cream, hospitals and sandwiches, but what about Dogecoin Core. Is the current pt-BR translation such an atrocity to a large amount of people that don't speak English and only speak pt-PT, that this is needed?

I'm okay with doing this inside the software translation, because that is something you see every time you use the software. The README on the other hand is something you won't read often and I am worried to set a precedent and ending up with dozens of readme translations that trail any change with a huge time gap and therefore become an obstacle to timely information.

Yes, I believe so.
In all my years of doing websites and using many open source scripts, because there are more Brazilian devs then Portuguese, If there is a Brazilian translation, people will mostly don't like to use it because is confusing, specially for kids and elderly.

For a coder/dev perspective, UK English is the only language needed, and so, any other language is not needed IMO, but because there is alredy a Brazilian translation, it should also have a Portuguese version of it, to welcome Portuguese devs also, its like showing the National Flag or sing the National anthem (a better way to see things) :)

[patricklodder]

I don't think this repository should be a place to host nationalism. If adding the Brazilian translation is deemed offensive by the 10M people from Portugal then perhaps we made a mistake and we need to consider removing all translations of the README.

[qlpqlp]

I don't think this repository should be a place to host nationalism. If adding the Brazilian translation is deemed offensive by the 10M people from Portugal then perhaps we made a mistake and we need to consider removing all translations of the README.

I actually see Portuguese from Portugal having a huge impact, so, actually I don't see your comment in anyway constructive to CORE, sorry.

I'm now asking someone from Portugal to review if that is OK with you.

[patricklodder]

We'll have a solution for this with the next release.

[patricklodder]

I've written a problem statement and proposal to fix re: those readme files in #3436

[qlpqlp]

I've written a problem statement and proposal to fix re: those readme files in #3436

Much thanks @patricklodder