Multi Portuguese Translations

[luizvaz]

We have two main Portuguese branches:

• Português (Portugal)
• Português (Brasil)

and two less known branches:

• Português (Angola)
• Português (Moçambique)

Too many differences in the written text turn unintelligible for readers of each region.
Simple examples:

• File in Portugal is Fichero, but in Brazil, it is Arquivo
• Mouse in Portugal is Rato, but in Brazil, it is Mouse
• Window in Portugal is Ventana, but in Brazil, it is Janela
• and so on ...

Said that there is any possibility of having multiple Translations?

[jonnathan-ls]

@luizvaz, In fact the comparison is a very valid observation, I'm just afraid of how much difference there is between the languages ​​in contrast to the effort of the complete translation to multi Portuguese languages

Anyway, this is an issue that was apparently discussed earlier in the repository and even mentioned by the javascript-info maintainer (@iliakan) himself: javascript-tutorial/en.javascript.info#1 issuecomment -491532555

Which apparently has a definition as per #1 (comment)

[jonnathan-ls]

Maybe... if an alternative to implement the application rendering logic that serves the platform... wouldn't be smoother.

For example: (the markdown file has element markup)

... <multi-language region="br"> text </multi-language> ...

So the server based on the element property, changes the value based on some configured repository list.

[iliakan]

The main thought behind making a single version was: "what's good for Wikipedia should be good for us".

[iliakan]

Is it safe to assume that most portuguese-speaking IT learners understand both Rato and Mouse, Ventana and Janela?

[jonnathan-ls]

Is it safe to assume that most portuguese-speaking IT learners understand both Rato and Mouse, Ventana and Janela?

I don't believe it's safe...

The terminology and pronunciation of the words are quite different, giving a margin of misinterpretation.

However, within a context, paying attention to where the word is inserted (paragraph as a whole), it ends up facilitating the interpretation of the word and consequently what is expected to be obtained from the reading.

[denissonstos]

Will there be a pt-br version? If so, I would like to help with that.

[pattuzzoj]

I believe that only translation to Portuguese of Brazil is sufficiently, because Portuguese countries have a rule to the whole language.

[jonnathan-ls]

@denissonstos I think that at the moment, we need to at least reach a goal of translating this ´pt´ repository itself so that it is promoted to production (since we don´t have it), I understand that if we stop to think about the multi-language of the Portuguese language, it would be just more complex for contributions to this repository

[RaphGL]

File in Portugal is Fichero, but in Brazil, it is Arquivo

Ficheiro not fichero, also if you say arquivo and show a path people will know what you mean.

Mouse in Portugal is Rato, but in Brazil, it is Mouse

If you say mouse people will also understand because it's basic english and people are familiar with brazilian portuguese

Window in Portugal is Ventana, but in Brazil, it is Janela

No that's not portuguese at all, ventana is spanish. Janela is Janela.

The differences are not big enough to make it unintelligle. Most European Portuguese and African Portuguese speakers (which are branches of the european variant) understand basic Brazilian Portuguese words. The dialects are closer than they are apart.

The terminology and pronunciation of the words are quite different, giving a margin of misinterpretation.

This is wrong. There are some small words where the meaning are opposites but most phrases/sentences mean exactly the same thing. This is like saying that an american will have trouble understanding text written by a british person because they speak a different dialect, when the dialects aren't that further apart unless you're looking at slang, spelling preferences, prefered ways of phrasing things, etc.

some european portuguese translated excerpt here to prove a point:

A linguagem JavaScript foi inicialmente criada para navegadores web. Desde então, ela se tem tornado numa linguagem com muitos usos em várias plataformas.

A plataforma pode ser um browser, um servidor ou outra plataform, ou até uma máquina de café "inteligente". Cada uma delas com funcionalidades especificas dessa plataforma. A especificação do JavaScript chama-os de plataforma hospedeira.

Uma plataforma hospedeira oferece os seus próprios objetos e funções para além do núcleo da linguagem. Os navegadores web oferecem uma forma de controlar as páginas web. O Node.js oferece funcionalidades para servidores e assim por diante.

[Peruibeloko]

I fully agree with @RaphGL.

I also came across this on one of my PRs and I believe there is an argument for keeping translations of different dialects.

I'm Brazilian, and as such, I will prioritize the Brazilian Portuguese translations of words, as it is my mother tongue and is the one I know best and will use to create the best translation I can.

I believe we shouldn't strive for the "one true Portuguese" interpretation, but rather have a mutually intelligible version, where we keep regional variations around, as long as they don't hinder the legibility for anyone.

As is the case of "caractere", which isn't that far off from "character" and also more naturally maps to the plural "caracteres" better than Portugal's "carácter".

Shouldn't we look at how Spanish solved this? They have the same problem with different dialects.