Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Portuguese (Brazil) Translation Progress #1

Closed
90 tasks done
tesseralis opened this issue Feb 8, 2019 · 251 comments
Closed
90 tasks done

Portuguese (Brazil) Translation Progress #1

tesseralis opened this issue Feb 8, 2019 · 251 comments

Comments

@tesseralis
Copy link
Member

tesseralis commented Feb 8, 2019 •
edited by jhonmike

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
Copy link
Contributor

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

@ericp3reira
Copy link
Contributor

May I translate Introducing JSX? :)

@iagobruno
Copy link

I'll translate the Conditional Rendering page

@tesseralis
Copy link
Member Author

@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
Copy link
Contributor

“Rendering elements” then?

@gnuns
Copy link
Contributor

gnuns commented Feb 8, 2019

Hi! I want to work on the Home Page

@klzns
Copy link
Contributor

klzns commented Feb 8, 2019

I would like to work on "Introducing Hooks"

@ifdiego
Copy link
Contributor

ifdiego commented Feb 8, 2019 •
edited

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

@rafaelquintanilha
Copy link
Contributor

rafaelquintanilha commented Feb 8, 2019 •
edited

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

@welll
Copy link
Contributor

welll commented Feb 8, 2019

Hi, I can translate Composition vs Inheritance

@iagobruno
Copy link

iagobruno commented Feb 8, 2019 •
edited

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
Copy link
Member Author

@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
Copy link
Member Author

@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
Copy link
Member

@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
Copy link

Hi I can do the Accessibility page

@glaucia86
Copy link
Member

@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
Copy link
Member

@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
Copy link

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

@tesseralis
Copy link
Member Author

tesseralis commented Feb 8, 2019 •
edited

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
Copy link
Member

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
Copy link
Contributor

nsouzaco commented Feb 8, 2019

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

@tesseralis tesseralis reopened this Feb 8, 2019
@iagobruno iagobruno mentioned this issue Feb 8, 2019
Merged
@eduardomoroni
Copy link
Member

eduardomoroni commented Feb 8, 2019 •
edited

@tesseralis I can translate Home Page and Tutorial.
[EDITED]
Noticed that someone is translating the Home page #2

@mllustosa
Copy link

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

@telmogoncalves
Copy link
Collaborator

telmogoncalves commented Feb 8, 2019 •
edited

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

@jhonmike
Copy link
Member

jhonmike commented Feb 8, 2019 •
edited

Hi, can I translate State and Lifecycle :)

@WendellAdriel
Copy link
Member

@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
Copy link
Member

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

@WeslleyNasRocha
Copy link
Contributor

i will translate the virtual dom and internals, pr later today

@Duduzera1997
Copy link
Contributor

Hello!
I can translate Community / Support ?

@glaucia86
Copy link
Member

Hello!
I can translate Community / Support ?

Could you?! Wow! Sure!

@glaucia86
Copy link
Member

@thiagoarmede hurry up!

i guess his page passed on another translator: @jhonesgoncal
#112 (comment)

but still, 5 days no pr

Já te atribui. Pode pegar essa PR :)

@lucianomlima
Copy link
Contributor

@Duduzera1997 @WeslleyNasRocha será que conseguimos finalizar essa tradução até amanhã (domingo 10/03)?
Não entendam como uma cobrança!

@Duduzera1997
Copy link
Contributor

@Duduzera1997 @WeslleyNasRocha será que conseguimos finalizar essa tradução até amanhã (domingo 10/03)?
Não entendam como uma cobrança!

Com certeza!

@WeslleyNasRocha
Copy link
Contributor

WeslleyNasRocha commented Mar 11, 2019 •
edited

#159 tai a primeira versão do DOM Virtual e Objetos Internos

@tesseralis
Copy link
Member Author

Congrats on finishing the core pages!
Screen Shot 2019-03-11 at 12 21 14 PM

Duduzera1997 added a commit to Duduzera1997/pt-br.react.dev that referenced this issue Mar 13, 2019
@Duduzera1997
Update errors reactjs#1.
ab2ef5f 
Alterado de "Rect" pra "React" na linha 23.
@jhonmike
Copy link
Member

I just merge the last translated page, can we mark the issue as done?

@tesseralis
Copy link
Member Author

@jhonmike yup, I think so... we already have an issue to track translating the blog, and maybe we can make another one for tracking the translation of the Community section?

@glaucia86
Copy link
Member

@jhonmike yup, I think so... we already have an issue to track translating the blog, and maybe we can make another one for tracking the translation of the Community section?

it will be awesome if we do that.

@glaucia86
Copy link
Member

Pessoal! A tradução da documentação do Reactjs.org já está 100% completa. Antes de mais nada, gostaria de agradecer a todos aqui pela ajuda prestada! Foi lindo tudo o que aconteceu aqui! Vocês e nós da Comunidade Técnica - são demais!

Parabéns a todos! E muito obrigada!

bitmoji

@PHPINHEIRO
Copy link

Pessoal, primeiramente eu gostaria de parabenizar pela iniciativa que tiveram, eh muito interessante para pessoas q n tem o domínio do inglês e querem aprender uma ferramenta nova, mas a doc da mesma só tem em imgles. Novamente parabéns a vocês. Aproveitando gostaria de perguntar se vocês irão extender para a doc do react native, caso sim, como faço pra contribuir?

@0xc41qu3
Copy link

0xc41qu3 commented Mar 28, 2019 •
edited

Hey guys!!

I'd like to translate the 2017-11-28-react-v16.2.0-fragment-support.md.
Could anyone assign me please ;)

@jhonmike
Copy link
Member

@CaiqueMOliveira consegue comentar na issue: #151

@lucaspolizeli lucaspolizeli mentioned this issue Apr 10, 2019
Closed
12 tasks
@glaucia86 glaucia86 mentioned this issue Jun 10, 2019
Closed
@renanmav
Copy link
Contributor

Posso traduzir o post introducing-relay-and-graphql?

@jhonmike
Copy link
Member

@renanmav pode sim, criei a issue dela aqui >> #302

@evaldosantos
Copy link
Contributor

Posso traduzir o post relay-state-of-the-state?

@jhonmike
Copy link
Member

jhonmike commented Oct 6, 2019

@evaldosantos pode iniciar a tradução, eu marquei seu nome na task de tradução do blog.

@jhonmike
Copy link
Member

jhonmike commented Oct 7, 2019

Galera vou fechar essa issue, e vou criar uma nova focada apenas nas novas paginas que precisam ser traduzidas 🤘

@jhonmike jhonmike closed this as completed Oct 7, 2019
@jhonmike jhonmike unpinned this issue Oct 17, 2019
@glaucia86 glaucia86 mentioned this issue Nov 6, 2019
Closed
@jhonmike jhonmike mentioned this issue Mar 2, 2020
Closed
@glaucia86 glaucia86 mentioned this issue May 21, 2020
Closed
@pedrohyvo
Copy link

Olá pessoal, quem tiver interesse em contribuir na tradução da documentação oficial do framework cypress.io, só acessar esse repositório aqui.

rickhanlonii pushed a commit that referenced this issue Apr 19, 2023
@renancouto
Fix legacy link (#1)
7863b5b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests