Portuguese (Brazil) Translation Progress

[tesseralis]

Maintainer List

• @cezaraugusto
• @eduardomoroni
• @fjoshuajr
• @glaucia86
• @gmsecrieru
• @halian-vilela
• @jcserracampos
• @tibuurcio
• @WendellAdriel
• @jhonmike

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:

• Home Page (@tesseralis) Portuguese (Brazil) Translation Progress #1

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.

• Home Page (@gnuns) (Translate Home Page #113)
• Tutorial (@eduardomoroni & @halian-vilela) (Translate Tutorial 1 of 2 #33 and Translate Tutorial 2 of 2 #68)

Basics ✅ Completed

• Hello World (@rafael-vitor) (Translate Hello World #57)
• Introducing JSX (@ericp3reira) (Translate introducing jsx #47)
• Rendering Elements (@mathsalmi) (Translate Rendering Elements #49)
• Components and Props (@ifdiego) (Translate Components and Props #23)
• State and Lifecycle (@jhonmike) (Translate state and lifecycle page #39)
• Handling Events (@httpiago) (Translation of the "Handling Events" page #3)
• Conditional Rendering (@cstpk) (Conditional Rendering translation #51)
• Lists and Keys (@WendellAdriel) (Translation Lists and Keys page #7)
• Forms (@httpiago) (Translation of Forms page #100)
• Lifting State Up (@gustavobini) (Translate Lifting State Up #96)
• Composition vs Inheritance (@welll) (Translate composition-vs-inheritance #136)
• Thinking in React (@rafaelquintanilha) (Translate Thinking in React #83)

API Reference ✅ Completed

• React (@renato-bohler)(Translate React API Reference #31)
• React.Component (@rcantuario) (Translating reference-react-component #130)
• ReactDOM (@michellocana) (ReactDOM page translation #48)
• ReactDOMServer (@fjoshuajr) (Translation ReactDOMServer page #10)
• DOM Elements (@tiagohermano) (Translate DOM Elements #45)
• SyntheticEvent (@cezaraugusto) (Translate SyntheticEvent #22)
• Test Utilities (@luizbraga) (Translate Test Utilities #81)
• Shallow Renderer (@henriquejensen) (Translate Shallow renderer #32)
• Test Renderer (@fjoshuajr) (Translation of Reference test renderer #116)
• JS Environment Requirements (@koka0012) (Translation of the "JS Environment Requirements " page #8)
• Glossary (@evaldosantos) (Translate: Api Reference Glossary #63)

Navigation ✅ Completed

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

• tutorial/nav.yml (@jhonmike) (Ajuste do Menu e tradução dos menus laterais #135)
• docs/nav.yml (@jhonmike) (Ajuste do Menu e tradução dos menus laterais #135)

Next Steps

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

Installation ✅ Completed

• Getting Started (@lucianomlima) Translate getting started #126
• Add React to a Website (@ukita) (Translate: Add React to a Website #54)
• Create a New React App (@mrcelo) (Translate Create a new React App page #18)
• CDN Links (@leandrocustodio) (Translating the document "cdn-links.md" to PT-BR #21)

Hooks ✅ Completed

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

• Introducing Hooks (@klzns) (Translate Introducing Hooks #72)
• Hooks at a Glance (@gabrielbs) (Translate Hooks Overview #80)
• Using the State Hook (@vinicius98s) (Translation for Using the State Hook #108)
• Using the Effect Hook (@WeslleyNasRocha) (Effect Hook page #117)
• Rules of Hooks (@thadeu) (Hooks / Rules of Hooks #11)
• Building Your Own Hooks (@WendellAdriel) (Building Your Own Hooks page translation #78)
• Hooks API Reference (@thadeu) (Rules / Hooks reference #76)
• Hooks FAQ (@thefrontendwizard) (Feat/hooks faq translation #115)

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.

• dont-call-proptypes (@matheusmonte) (Translate page dont-call-proptypes.md  #19)
• invalid-aria-prop (@andrescalco) (Add pt-BR translation to the invalid-aria-prop page #24)
• invalid-hook-call-warning (@henriquejensen) (Translates Invalid hook call warning #52)
• legacy-factories (@juliofortunato) (Translate Legacy Factories warning #88)
• refs-must-have-owner (@GCrispino) (Translate warnings/refs-must-have-owner.md #59)
• special-props (@andrescalco) (Special props translation #28)
• unknown-prop (@crisgon) (Translated unknown-prop page to PT-BR. #44)

Advanced Guides ✅ Completed

• Accessibility (@LucasVilela) (Adding PT-BR to Accessibility page #74)
• Code-Splitting (@lucianomlima) Translate code-splitting page #140
• Context (@jancassio) (Translation: Context #55)
• Error Boundaries (@fmoliveira) (Translate Error Boundaries #73)
• Forwarding Refs (@taynancid) (Translation of Fowarding Refs Page  #64)
• Fragments (@gustavoaz7) (Translate Fragments #13)
• Higher-Order Components (@victorfsf) (Translate Higher-Order Components #77)
• Integrating with Other Libraries (@thulioph) (Translate Integrating With Other Libraries #82)
• JSX In Depth (@murtinha) (Translate jsx-in-depth to pt-BR #105)
• Optimizing Performance (@boniattirodrigo) (Translate Optimizing Performance #110)
• Portals (@Rahmon) (Translate Portals to pt-BR #97)
• React Without ES6 (@gutofoletto) (React without ES6 #95)
• React Without JSX (@tibuurcio) (Translate React without JSX #56)
• Reconciliation (@victorsilent) (Translate reconciliation #41)
• Refs and the DOM (@steniowagner) (Translating the refs-and-the-dom page #40)
• Render Props (@italotabatinga) (Translate Render Props #94)
• Static Type Checking (@ericp3reira) (Translate static type checking #103)
• Strict Mode (@lffg) (Translate strict-mode.md to pt-BR #25)
• Typechecking With PropTypes (@lucasdeassis) (Translate Typechecking with Proptypes page #17)
• Uncontrolled Components (@arthur-souza) (Translate uncontrolled-components #53)
• Web Components (@thealexandrelara) (Translate Web Components page #27)

FAQ ✅ Completed

• APIs and AJAX (@lazaroalvarenga) (Translation of the "AJAX and APIs" page #9)
• Babel, JSX, and Build Steps (@GleidsonDaniel) (Translation of the "Babel, JSX, and Build Steps" page #12)
• Passing Functions to Components (@negreirosleo) (Translate Passing Functions to Components #16)
• Component State (@vhfmag) (Traduzir "Estado de componente" no FAQ #129)
• Styling and CSS (@rhiroyuki) (Translate Styling and CSS to pt-BR #36)
• File Structure (@RodolfoSilva) (Translate FAQ > File Structure page to pt-BR #37)
• Versioning Policy (@elainemattos) (Versioning policy #148)
• Virtual DOM and Internals (@WeslleyNasRocha) (DOM Virtual e Objetos Internos #159)

Contributing ✅ Completed

Priority: Low

• How to Contribute (@lhcgoncalves) (How to contribute #138)
• Codebase Overview (@lamecksilva) (codebase-overview translate #43)
• Implementation Notes (@Luanf) (Translating Implementation Notes #146)
• Design Principles (@moiseshilario) (Translate Design Principles #60)

Components ✅ Completed

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

• CodeEditor (@abnersajr) (Translate CodeEditor #20)
• CodeExample (@luizcieslak) (Translate CodeExample.js #30)
• ErrorDecoder (@halian-vilela) (Translate ErrorDecoder to pt-BR #29)
• LayoutFooter (@gstvribs) (Translate LayoutFooter to pt-BR #84)
• LayoutHeader (@thealexandrelara) (Translate LayoutHeader Component #89)
• MarkdownPage (@lucianomlima) (Translate some texts in several pages #145)

Additional Translations

These are not the primary translation targets.

• Blog (Progresso de tradução do Blog #151)
• Community
  • Tools: (@crisgon) (Community tools #106)
  • Resources: (@Duduzera1997) (Support Traduzido a página Community/Support (Comunidade/Suporte) #152, Courses Translated Community/Courses; #158, Examples Translated "Community/Examples"; #164, Meetups Translated "Community/Meetups"; #169, Conferences Translated React v16.6.0: lazy, memo and contextType #179, Articles Translated "Community/Articles"; #184)

[rafael-vitor]

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

[ericp3reira]

May I translate Introducing JSX? :)

[iagobruno]

I'll translate the Conditional Rendering page

[tesseralis]

@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]

“Rendering elements” then?

[gnuns]

Hi! I want to work on the Home Page

[klzns]

I would like to work on "Introducing Hooks"

[ifdiego]

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

[rafaelquintanilha]

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

[welll]

Hi, I can translate Composition vs Inheritance

[iagobruno]

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]

@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]

@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]

@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]

Hi I can do the Accessibility page