ropensci / dev_guide

rOpenSci Packages: Development, Maintenance, and Peer Review
https://devguide.ropensci.org
Creative Commons Attribution Share Alike 4.0 International
159 stars 55 forks source link

Review for Portuguese translation of `maintenance_cheatsheet.pt.Rmd` #717

Closed pedropark99 closed 9 months ago

pedropark99 commented 10 months ago

This PR brings three change to the automatic output generated by the translation tools:

In respect to the word "cheatsheet", the API translated it into "Folha de dicas", which is not a bad choice, but maybe... just maybe, is better to use "Cola" instead, which is a more direct translation of the "cheatsheet" word. But I will leave this choice to whoever will do the Review 2.

pedropark99 commented 10 months ago

@joaojcorreia and @danielvartan This PR is ready for Review 2.

danielvartan commented 10 months ago

Great! I will have some time tomorrow to start the review.

joaojcorreia commented 10 months ago

Given that @danielvartan had already volunteered, I assume I won't be needed now. However, I suggest you keep "folha de dicas", as "cola" won't be understood in PT-PT, and i presume "cábula" won't be in PT-BR.

pedropark99 commented 10 months ago

Good point @joaojcorreia , thank you!

danielvartan commented 10 months ago

Changed the use of the word "comiseração" (which was translated from "commiseration") to "papo". Because "comiseração" is an obscure word in our language, is not really used or known by many people. So I opted to use a much popular word that kinds of translates the idea (I'm open to better suggestions than "papo"). @pedropark99

Just leaving this here if someone is curious about it. 😂


comiseração

co·mi·se·ra·ção sf

1 Ato de comiserar-se. 2 Compaixão pelos infortúnios alheios.

Source: Michaelis \<https://michaelis.uol.com.br/busca?id=lW1m >.


comiserar

co·mi·se·rar vtd 1 Fazer sentir comiseração ou piedade. vpr 2 Sentir-se compadecido

Source: Michaelis \<https://michaelis.uol.com.br/busca?r=0&f=0&t=0&palavra=comiserar >.

danielvartan commented 10 months ago

@pedropark99 I just finished reading the translation guidelines. I plan to do the review tomorrow.

It's not clear to me what the preferred method for submitting changes in the 2nd review is. Do you prefer that I simply comment on the changes using the review tools in the PR, or commit the changes in the fork? In the latter case, according to the guidelines, I would need to have permission to write on it.

Regarding the title (@joaojcorreia), perhaps it's a good idea to use a solution closer to the Spanish translation used in rOpenSci Glossary (see here), don't you think?

cheatsheet, guía rápida,,
cheat sheet, guía rápida,,
joaojcorreia commented 10 months ago

I would go with "guia rápido". As it is self-describing and I believe understandable for all.

joaojcorreia commented 10 months ago

Adding to my previous comment and addressing @danielvartan comment about "comiseração". I agree with Daniel, this is an obscure term not regularly used in day-to-day contexts. However, "papo" isn't in my view an adequate alternative.

Just for context, "papo" is an ornithological term meaning a bird crop. In PT-BR the term evolved into meaning an open conversation, yet in PT-PT it still means a bird crop. I would suggest "uma conversa amigável".

Additionally, I would avoid the usage of "você". "Você" is a contraction of "vossa mercê", an archaic form of respect. In PT-BR it evolved into a coloquial form of referring to "you", yet in PT-PT it evolved into a condescending way of exhibiting fake respect. I would suggest we abstain from using "você", and just conjugate the verb in the third person of the singular leaving the noun implicit.

Please don't misinterpret my comments. I understand that we may not always be fully aware of our individual use of localisms. If you wish, I would be happy to go over the document to tweak it to a neutral version of Portuguese.

pedropark99 commented 10 months ago

Fist point, I liked the option of using "guia rápido".

Now, regarding the doubt of @danielvartan about the review process. The guidelines for review 2 talks about pulling the latest changes, and working in the branch associated with the file that is being translated. So I understand that you need to clone my fork, git switch to my branch that is associated with this PR, and do the changes there, and then, commit them. However, if you find appropriate, I do not have problems with you reviewing by just using the PR Review tools, which are quite handy.

@yabellini can you help me to advise @danielvartan better in this subject?

pedropark99 commented 10 months ago

Second point, I also liked the suggestion @joaojcorreia of using "conversa amigável" instead of "papo".

About the points raised about the word "você", when you say:

and just conjugate the verb in the third person of the singular leaving the noun implicit.

I think it would add to the discussion if you give an example of a phrase in both states, using the third person, and not using the third person. This way you present your idea in the most clear way as possible.

Besides that, I understand that this idea of avoiding the use of "você" with the objective of reaching to a more "neutral" portuguese is aligned with the translation objectives. And for that, I think we will need great help of you @joaojcorreia to reach this objective.

joaojcorreia commented 10 months ago

To materialize what I am saying about "você":


Você também pode usar o nosso canal de manutenção de pacotes no Slack.

Would become:

Pode, também, usar o nosso canal de manutenção de pacotes no Slack.

Você deve ter acesso administrativo ao repositório do GitHub do seu pacote.

would become:

Deverá ter acesso administrativo ao repositório do GitHub do pacote.


Se você tiver alguma pergunta ou solicitação sobre o GitHub (por exemplo, adicionar um colaborador à organização do GitHub), você pode usar um dos canais públicos no Slack do rOpenSci ou enviar uma mensagem para @ropensci/admin no GitHub.

would become:

Se tiver alguma pergunta ou solicitação sobre o GitHub (por exemplo, como adicionar um colaborador à organização do GitHub), deverá usar um dos canais públicos no Slack do rOpenSci ou enviar uma mensagem para @ropensci/admin no GitHub.


I think this way it will be clear for all.

danielvartan commented 10 months ago

Thank you for the responses, @pedropark99 and @joaojcorreia.

@pedropark99, regarding the changes, as you said, I will fork and commit them.

About the title. 'Guia rápido' has an agreement issue, as it's a feminine noun. It should be 'guia rápida.'

Regarding 'você,' I respectfully disagree with you, @joaojcorreia. I understand your point, but we must also consider that the vast majority of Portuguese speakers are Brazilians. By omitting 'você' from the translations, the text looks very weird, approaching it to Portugal Portuguese speakers but distancing itself from Brazilian speakers.

As the guidelines also state, we must choose one style for the language, aiming to include all people in the process. However, we can't do this by undermining the primary style. In Spanish, this is the Latin American style. In Portuguese, this should be the Brazilian style.

danielvartan commented 10 months ago

It's also important to remember that the language is alive. I understand the evolution of the word 'você' from 'vossa mercê.' It's the first thing we learn when studying Portuguese literature, but today, no Brazilians think that way.

For Brazilian speakers, 'você' is used just like 'you' in English (formal and informal use), and, unlike in Portugal, the second-person singular 'tu' is rarely used. If we want to be understood by most Portuguese speakers, we shouldn't consider omitting 'você.' Also, 'você' is gender-neutral.

pedropark99 commented 10 months ago

@danielvartan raised a good point about "você". I understand we have two choices here in this subject:

  1. Find a middle ground. That is, to find a word (or a sentence structure) that can substitute "você", and that is: 1) familiar to most brazilians; 2) also used in PT-PT; 3) a good-enough representation of "you".
  2. Prioritize whatever choice that fits best into the translation guidelines and objetives.

Perhaps @yabellini can help us to decide which of these two options above we should pursue. I think that we should focus on the option 2.

danielvartan commented 10 months ago

I believe that @joaojcorreia is correct in arguing against the use of "você" in certain cases. My disagreement lies in the idea of completely avoiding it. There are sentences where a pronoun is unnecessary.

For example: Você precisa de ajuda? conveys the same meaning (at least for Brazilian speakers) as Precisa de ajuda?.

However, consider the case raised by @joaojcorreia:

Você deve ter acesso administrativo ao repositório do GitHub do seu pacote.Deverá ter acesso administrativo ao repositório do GitHub do pacote.. This simply doesn't sound natural.

In short, I believe that fluency should be one of the primary considerations, in line with the first general guideline ("Use a conversational voice rather than a formal or academic voice"). If you can maintain fluency without using pronouns, great! Don't use them. However, if a pronoun enhances fluency, then it should be used.

danielvartan commented 10 months ago

Jumping to another subject.

Are we using a masculine article or a feminine article when referring to rOpenSci?

I usually think rOpenSci as an organization. Since "organização" is a feminine noun, I believe it must be referred with the article "a".

For example:

Veja Documentos do rOpenSci.

Should be :

Veja a seção Documentos da rOpenSci.

danielvartan commented 10 months ago

@pedropark99 I have submitted a PR with the review changes. Please take a look at it when you have some time.

There were a lot of small things to consider. The next translations may be faster. 😁

pedropark99 commented 10 months ago

Thank you @danielvartan ! ❤

pedropark99 commented 10 months ago

Thank you for the review @danielvartan ! @maelle I understand this PR is ready to merge (reviews 1 and 2 done) 😉.

marianambc commented 10 months ago

Hi, here Mariana (from Lisbon), happy to help with the review process as well. Thank you.

yabellini commented 10 months ago

Hello, thank you very much for all this work and the beautiful discussion about the best way to translate the guide. I'm sorry for not getting back to you sooner, lots of traveling this month.

Each language is free to discuss and decide the rules for better localization and translation of the content. You have already seen some of the rules we have in Spanish that can be used in the Portuguese translation. For Spanish, we use some of the agreements that other translations did about Spanish. Perhaps @beatrizmilz can share some guidelines with us?

You already see the general rules (like conversational language, trying to avoid gender marks, etc), so I think these are very valuable discussions. You are native speakers, so you are better equipped to make a decision than I am.

If you share with me your emails I will send an invite to our Slack (if you are not already there) and I will also create a channel for this translation, and you can discuss these details there too.

We should write these rules and agreements in Portuguese and incorporate them into the guidelines.

Thanks so much for doing this important work!

beatrizmilz commented 10 months ago

Hi! This presentation lists two other translation projects: https://docs.google.com/presentation/d/1uqsPo715R_r0u6wPyC3EBbUVkri0qjf7SV5Y-zTfTZ0/edit?usp=sharing One thing that is pointed out at the end of this presentation is that it would be great to have a "main guide" for translations, so it is easier to start a new translation project, and the translations follow similar guidelines. But we don't have something like that yet.

This is the guide for the R base translation:

https://contributor.r-project.org/translations/Conventions_for_Languages/Brazilian%E2%80%90Portugese-specific-translations.html

This is the guide for the translation of the R for Data Science book: https://github.com/cienciadedatos/pt-r4ds/wiki/3-%E2%80%90-Guia-de-contribui%C3%A7%C3%A3o-com-a-tradu%C3%A7%C3%A3o-do-livro-%22R-for-Data-Science-(2e)%22 (this is growing as we translate)

danielvartan commented 10 months ago

Great initiative, @beatrizmilz! I'll try to help as I can.

marianambc commented 10 months ago

Thank you for all the documents, I'll be looking into it later today and tomorrow. Thanks!

On Mon, Oct 30, 2023 at 4:15 PM Daniel Vartanian @.***> wrote:

Great initiative, @beatrizmilz https://github.com/beatrizmilz! I'll try to help as I can.

— Reply to this email directly, view it on GitHub https://github.com/ropensci/dev_guide/pull/717#issuecomment-1785965822, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSTPFVN7KVLRL4EXLNS653YCADHRAVCNFSM6AAAAAA6LFR7C2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVHE3DKOBSGI . You are receiving this because you commented.Message ID: @.***>