search

reactjs / pt-br.react.dev

🇧🇷 React documentation website in Portuguese (Brazil)
https://pt-br.react.dev
Creative Commons Attribution 4.0 International
487 stars 309 forks source link

Portuguese (Brazil) Translation Progress #1

Closed tesseralis closed 5 years ago

tesseralis commented 5 years ago

Maintainer List

For New Translators

To translate a page:

  1. Check that no one else has claimed your page in the checklist and comments below.
  2. Comment below with the name of the page you would like to translate. Take only one page at a time.
  3. Clone this repo, translate your page, and submit a pull request!

Before contributing, read the glossary to understand how to translate various technical and React-specific terms.

Please be prompt with your translations! If you find find that you can't commit any more, let the maintainers know so they can assign the page to someone else.

Discord room

https://discord.gg/Zn4bXAz

For maintainers

When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:

When PRs are merged, make sure to mark that page as completed!

Core Pages

To do before releasing as an "official" translation. Please translate these pages first.

Basics ✅ Completed

API Reference ✅ Completed

Navigation ✅ Completed

These are the navigation links that appears in the sidebar. Possibly wait until the corresponding sections are translated to do these.

Next Steps

These are the next most important translations, ordered by importance:

Installation ✅ Completed

Hooks ✅ Completed

Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.

Warnings ✅ Completed

These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.

Advanced Guides ✅ Completed

FAQ ✅ Completed

Contributing ✅ Completed

Priority: Low

Components ✅ Completed

Components in src/components that have some text in them.

Additional Translations

These are not the primary translation targets.

rafael-vitor commented 5 years ago

Hello World Hey, I'd like to help. I'll take the Hello World page on the basics section. Ok?

ericp3reira commented 5 years ago

May I translate Introducing JSX? :)

iagobruno commented 5 years ago

I'll translate the Conditional Rendering page

tesseralis commented 5 years ago

@rafael-vitor @ericp3reira @httpiago I gave you the sections you requested!

@mathsalmi could you pick another section?

@cezaraugusto @jcserracampos @WendellAdriel make sure you follow this issue and update it when people volunteer!

mathsalmi commented 5 years ago

“Rendering elements” then?

gnuns commented 5 years ago

Hi! I want to work on the Home Page

klzns commented 5 years ago

I would like to work on "Introducing Hooks"

ifdiego commented 5 years ago

Hey, I can help! I would like the Components and Props section.

rafaelquintanilha commented 5 years ago

Hello! I'd like to translate Thinking in React.

welll commented 5 years ago

Hi, I can translate Composition vs Inheritance

iagobruno commented 5 years ago

I can not translate the whole page, there are some parts with red text that I can not edit, so I'll go to another page: Handling Events.

tesseralis commented 5 years ago

@httpiago what do you mean "red text I can't edit"? Please only request a page at a time. I gave you "Handling Events" for now.

tesseralis commented 5 years ago

@httpiago Ah, we're not editing the text directly in Crowdin -- it's just a reference to make your work easier. You should do your translations directly in the source code! Either directly edit the file here by clicking the pencil icon or clone this repository and work on it on your preferred text editor.

cezaraugusto commented 5 years ago

@tesseralis ok if I split this issue into each part with its own issue? my plan is to have an issue covering in checkboxes each page heading for example. this could speed up the process as it is less text to translate and so less effort from maintainers to review.

from past experience, anything bigger than 2 paragraphs can take months to finish due to work/life/motivation loss and this plan tries to avoid a page being stuck with someone longer than it could be while others could contribute.

LucasVilela commented 5 years ago

Hi I can do the Accessibility page

glaucia86 commented 5 years ago

@httpiago Ah, we're not editing the text directly in Crowdin -- it's just a reference to make your work easier. You should do your translations directly in the source code! Either directly edit the file here by clicking the pencil icon or clone this repository and work on it on your preferred text editor.

I will explain about it right now in portuguese to everyone.

"Pessoal, todos aqui devem fazer um fork desse repositório e após isso, criar uma PR de acordo com a lista criada pela @tesseralis e assignar o seu nome ao lado da contribuição que realizará, juntamente com o número da PR. Quando a @tesseralis mencionou o Crowdin, foi com a intenção de vocês darem uma olhada como foi feita a tradução anterior. As novas serão realizadas via Git ;)"

@cezaraugusto o que acha de criarmos uma outra Issue para discutir as traduções em pt? ou mantem essa aqui mesmo?

glaucia86 commented 5 years ago

@tesseralis ok if I split this issue into each part with its own issue? my plan is to have an issue covering in checkboxes each page heading for example. this could speed up the process as it is less text to translate and so less effort from maintainers to review.

from past experience, anything bigger than 2 paragraphs can take months to finish due to work/life/motivation loss and this plan tries to avoid a page being stuck with someone longer than it could be while others could contribute.

Wow.. I was thinking in the same thing right now! :) We are conected it! :)

iagobruno commented 5 years ago

@tesseralis Ah, I had not seen any forks so I thought the translation was being sent in Crowdin. 😂 No problem now

tesseralis commented 5 years ago

Ahh... I think I'd rather have it stay in one page, just so we can get an overall goal on the translation progress (and I'm also trying to get a progress tracker going that relies on having a whole issue for the translation).

We don't need to translate the entire thing before releasing the first version -- just the pages labelled "Core Pages". I don't think people have gotten dissuaded so far: it's been a week and both the Japanese and Spanish translations are almost done with the Core Pages!

I think splitting might make some things easier but it can make other things harder too. It's harder to make sure that people aren't taking more than one issue, for example.

Let's keep the one page for now and if you're finding it too cumbersome in a few days, I'll reconsider!

glaucia86 commented 5 years ago

Ahh... I think I'd rather have it stay in one page, just so we can get an overall goal on the translation progress (and I'm also trying to get a progress tracker going that relies on having a whole issue for the translation).

We don't need to translate the entire thing before releasing the first version -- just the pages labelled "Core Pages". I don't think people have gotten dissuaded so far: it's been a week and both the Japanese and Spanish translations are almost done with the Core Pages!

I think splitting might make some things easier but it can make other things harder too. It's harder to make sure that people aren't taking more than one issue, for example.

Let's keep the one page for now and if you're finding it too cumbersome in a few days, I'll reconsider!

Ok

nsouzaco commented 5 years ago

Hi, I'd like to translate the Conditional Rendering page :)

eduardomoroni commented 5 years ago

@tesseralis I can translate Home Page and Tutorial. [EDITED] Noticed that someone is translating the Home page https://github.com/reactjs/pt-BR.reactjs.org/pull/2

mllustosa commented 5 years ago

I would like to translate Composition vs Inheritance and Thinking in React for now.

telmogoncalves commented 5 years ago

We'll have both pt-BR and pt-PT, or just pt-BR?

jhonmike commented 5 years ago

Hi, can I translate State and Lifecycle :)

WendellAdriel commented 5 years ago

@gnuns @klzns @ifdiego @rafaelquintanilha @welll @LucasVilela @cstpk @eduardomoroni @jhonmike

I gave you the ones you claimed above! 🤘

@mllustosa the items you said were already claimed by others, can you choose other items? 😉

WendellAdriel commented 5 years ago

@telmogoncalves this repository is only for the pt-BR translation, but if you want to, you can submit a PR on https://github.com/reactjs/reactjs.org-translation/ to create a team and a repo for the pt-PT.

renato-bohler commented 5 years ago

I would like to translate the whole Installation section (Getting Started, Add React to a Website, Create a New React App, CDN Links) to begin with :smiley:

tesseralis commented 5 years ago

On that note... are the variations different enough that it's important to maintain separate forks?

tesseralis commented 5 years ago

@renato-bohler We encourage people to only take one page at a time; and also, please try to pick one of the sections listed under "Core Pages"

WendellAdriel commented 5 years ago

@tesseralis I'm from Brazil, but I live in Portugal since 2016 and there are a lot of words that are different, but everyone here understands the Portuguese from Brazil, but I think that if someone wants to create a separated translation, maybe it's something to think about

renato-bohler commented 5 years ago

Oh :disappointed: can I translate API Reference > React then?

telmogoncalves commented 5 years ago

@WendellAdriel that was my point as well. I'm Portuguese and looking at the PRs, it does sound a little different from pt-PT, understandable, but different 😊

WendellAdriel commented 5 years ago

Just assigned that to you @renato-bohler!

tesseralis commented 5 years ago

@WendellAdriel gotcha! I know there's only one Spanish translation and I know there are definitely regional variations there. What do you all think? Should we keep pt-BR and add pt-PT later, or should we just have a single pt for now and s/você/tu later?

WendellAdriel commented 5 years ago

@tesseralis I think that we can keep the pt-BR and later when we have a team to create the pt-PT translation we can add that

WendellAdriel commented 5 years ago

@tesseralis I just created the first version of the Glossary #4, can you pin it? I think that I don't have the needed permissions to do so.

WendellAdriel commented 5 years ago

Also, for now, I'll translate Lists and Keys

tiagohermano commented 5 years ago

Can i get DOM Elements?

WendellAdriel commented 5 years ago

Done @tiagohermano!!! 😉

telmogoncalves commented 5 years ago

I'll work on the pt-PT translations than 😊

carolsoaressantos commented 5 years ago

I would like to translate the Installation Pages :) @tesseralis

WendellAdriel commented 5 years ago

Like @tesseralis said above, we are encouraging people to only take one page at a time, can I assign the Getting Started page to you for now @carolcodes ?

carolsoaressantos commented 5 years ago

Like @tesseralis said above, we are encouraging people to only take one page at a time, can I assign the Getting Started page to you for now @carolcodes ? Yes, please :)

WendellAdriel commented 5 years ago

Done @carolcodes!!! 😉

gustavobini commented 5 years ago

Can I take Lifting State Up?

michellocana commented 5 years ago

May i translate ReactDOM?

telmogoncalves commented 5 years ago

@WendellAdriel how can I make sure I'll be part of the pt-PT team once it's available? Just keeping an eye on it?

WendellAdriel commented 5 years ago

Done @gustavobini and @michellocana!!!

WendellAdriel commented 5 years ago

@telmogoncalves we need to confirm with @tesseralis, but I think that you can create a PR on the https://github.com/reactjs/reactjs.org-translation/ for the pt-PT translation, adding you to the list of maintainers