Comments (251)
@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!
from pt-br.react.dev.
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!
from pt-br.react.dev.
Hello World
Hey, I'd like to help. I'll take the Hello World page on the basics section. Ok?
from pt-br.react.dev.
@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.
from pt-br.react.dev.
I've opened a PR for pt-PT, we'll wait to add more maintainers and until it makes sense to merge.
from pt-br.react.dev.
Please, everyone that's already working on translations and the ones that will start now, take a look at #4 and any questions or suggestions, please use the Glossary issue to discuss!!! 😉
from pt-br.react.dev.
@WendellAdriel I would like to take ReactDOMServer.
@telmogoncalves Please let me know if you need help with the pt-PT, I'm from Mozambique and identify more with pt-PT than pt-BR. Depending on the number of the contributors in the pt-PT repo we could benefit from the translations from the folks here and just make a few tweaks?
I've added you as a maintainer in the PR 👍
from pt-br.react.dev.
Done @fmoliveira and @ukita!!! 😉
from pt-br.react.dev.
I would like to work on "Introducing Hooks"
from pt-br.react.dev.
@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.
from pt-br.react.dev.
@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?
from pt-br.react.dev.
@tesseralis Ah, I had not seen any forks so I thought the translation was being sent in Crowdin. 😂
No problem now
from pt-br.react.dev.
@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? 😉
from pt-br.react.dev.
@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 😊
from pt-br.react.dev.
Just assigned that to you @renato-bohler!
from pt-br.react.dev.
Done @tiagohermano!!! 😉
from pt-br.react.dev.
I would like to translate the Installation Pages :) @tesseralis
from pt-br.react.dev.
Done @CarolCodes!!! 😉
from pt-br.react.dev.
@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
from pt-br.react.dev.
Oh I see, @glaucia86.
For me it's ok, I just pointed out that because living here I know that the way we write in Brazil and here in Portugal can be very different sometimes. But as I also said, they can understand the differences. But if there's a team to translate to pt-PT, I don't see any issues with that 😉
from pt-br.react.dev.
I agree, @glaucia86. Every PR needs to be checked by at least two diff contributors and just after LGTM (two is a good number) and code review that we can approve to merge. Until now I think that we just got one PR to review, the other is a WIP and the other one is mine, but not related to translations.
from pt-br.react.dev.
Done, @lazaroalvarenga!!! 😉
from pt-br.react.dev.
I agree, @glaucia86. Every PR needs to be checked by at least two diff contributors and just after LGTM (two is a good number) and code review that we can approve to merge. Until now I think that we just got one PR to review, the other is a WIP and the other one is mine, but not related to translations.
do you know if the 'Settings' are prepare for these cases?
from pt-br.react.dev.
Done @gabrielbs and @luizbraga!!! 😉
from pt-br.react.dev.
Done @fjoshuajr!!! 😉
from pt-br.react.dev.
Can I take How to contribute page?
from pt-br.react.dev.
Can i take Codebase Overview page?
from pt-br.react.dev.
I would like to help on "Render Props"
from pt-br.react.dev.
Can I take API Reference / glossary page ?
from pt-br.react.dev.
Can I take the Using the State Hook?
from pt-br.react.dev.
Done @henriquejensen and @koka0012!!! 😉
@thadeu, this was already claimed before, can you please choose other?
from pt-br.react.dev.
@victorfsf assigned 👍
from pt-br.react.dev.
can I take
JSX In Depth
?
Assigned @murtinha 👍
from pt-br.react.dev.
May I translate Introducing JSX? :)
from pt-br.react.dev.
I'll translate the Conditional Rendering page
from pt-br.react.dev.
“Rendering elements” then?
from pt-br.react.dev.
Hi! I want to work on the Home Page
from pt-br.react.dev.
Hey, I can help!
I would like the Components and Props section.
from pt-br.react.dev.
Hello! I'd like to translate Thinking in React.
from pt-br.react.dev.
Hi, I can translate Composition vs Inheritance
from pt-br.react.dev.
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.
from pt-br.react.dev.
@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.
from pt-br.react.dev.
Hi I can do the Accessibility
page
from pt-br.react.dev.
@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! :)
from pt-br.react.dev.
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
from pt-br.react.dev.
Hi, I'd like to translate the Conditional Rendering page :)
from pt-br.react.dev.
@tesseralis I can translate Home Page and Tutorial.
[EDITED]
Noticed that someone is translating the Home page #2
from pt-br.react.dev.
I would like to translate Composition vs Inheritance and Thinking in React for now.
from pt-br.react.dev.
We'll have both pt-BR and pt-PT, or just pt-BR?
from pt-br.react.dev.
Hi, can I translate State and Lifecycle :)
from pt-br.react.dev.
@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.
from pt-br.react.dev.
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 😃
from pt-br.react.dev.
On that note... are the variations different enough that it's important to maintain separate forks?
from pt-br.react.dev.
@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"
from pt-br.react.dev.
@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
from pt-br.react.dev.
Oh 😞 can I translate API Reference > React then?
from pt-br.react.dev.
@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?
from pt-br.react.dev.
@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
from pt-br.react.dev.
@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.
from pt-br.react.dev.
Also, for now, I'll translate Lists and Keys
from pt-br.react.dev.
Can i get DOM Elements?
from pt-br.react.dev.
I'll work on the pt-PT translations than 😊
from pt-br.react.dev.
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 ?
from pt-br.react.dev.
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 :)
from pt-br.react.dev.
Can I take Lifting State Up?
from pt-br.react.dev.
May i translate ReactDOM?
from pt-br.react.dev.
@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?
from pt-br.react.dev.
Done @gustavobini and @michellocana!!!
from pt-br.react.dev.
Hey everyone, I would like to translate the " React.Component" section !
from pt-br.react.dev.
Done @rcantuario!!! 😉
from pt-br.react.dev.
@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.
In Portuguese Translation in node.js we mantain the same time core (pt-br and pt-pt) as you can see here:
The linguistic variations are so few with Brazilian Portuguese to Portugal.
I think we may follow the @tesseralis advice in just let this issue with pt (even to Brazilian Portuguese and Portuguese). And then if we see there will be a lot of linguistic variations changes, so we can think to open a issue for pt-PT.
What do you think about it? @cezaraugusto @tesseralis @WendellAdriel @telmogoncalves ?
from pt-br.react.dev.
@WendellAdriel even be part of moderation time in pt-BR, I will help to translate a few pages. I already assigned myself.
But as we already do in Time Core Translation in nodejs.org, we just will approve a PR after two LGTM and code review?
cc: @cezaraugusto
from pt-br.react.dev.
Can I translate FAQ starting with APIs and AJAX
from pt-br.react.dev.
I can take the * Hooks at a Glance
from pt-br.react.dev.
Could I take "Test Utilities"?
from pt-br.react.dev.
@WendellAdriel I would like to take ReactDOMServer.
@telmogoncalves Please let me know if you need help with the pt-PT, I'm from Mozambique and identify more with pt-PT than pt-BR. Depending on the number of the contributors in the pt-PT repo we could benefit from the translations from the folks here and just make a few tweaks?
from pt-br.react.dev.
cc: @lamecksilva
Done. 👍
Already assigned it!
from pt-br.react.dev.
cc: @italotabatinga
Done. 👍
Already assigned it!
from pt-br.react.dev.
cc: @evaldosantos
Done. 👍
Already assigned it!
from pt-br.react.dev.
cc: @vinicius98s
Done. 👍
Already assigned it!
from pt-br.react.dev.
cc: @lhcgoncalves
Done. 👍
Already assigned it!
from pt-br.react.dev.
Can I take Shallow Renderer?
from pt-br.react.dev.
May I take JS Environment Requirements?
from pt-br.react.dev.
Can I take JS Environment Requirements or Rules of Hooks?
from pt-br.react.dev.
Done @henriquejensen and @koka0012!!! 😉
@thadeu, this was already claimed before, can you please choose other?
so, I take Rules of Hooks to translate
from pt-br.react.dev.
may i take the Using the Effect Hook
from pt-br.react.dev.
Done @thadeu and @WeslleyNasRocha!!! 😉
from pt-br.react.dev.
Hi, can I take Error Boundaries?
from pt-br.react.dev.
Hi, can I work on Add React to a Website? 👋
from pt-br.react.dev.
Hi! Can I take Higher-Order Components
?
from pt-br.react.dev.
can I take JSX In Depth
?
from pt-br.react.dev.
Hi! May I take Create a New React App
?
Edit: PR #18
from pt-br.react.dev.
@WendellAdriel Can I work in the Hooks API Reference
now?
from pt-br.react.dev.
The page Babel, JSX, and Build Steps
is mine! 👀
Ok?
from pt-br.react.dev.
@mrcelo @thadeu @GleidsonDaniel assigned, thanks!
from pt-br.react.dev.
Can I take Code-splitting
?
from pt-br.react.dev.
Done @wagnermoschini!!! 😉
from pt-br.react.dev.
Can I take Fragments
& Typechecking With PropTypes
?
from pt-br.react.dev.
I assigned Fragments
to you @gustavoaz7, when you finish that one, you can take another, we are encouraging people to work on one page at a time!!! 😉
from pt-br.react.dev.
Hi. Can I take Portals?
from pt-br.react.dev.
Related Issues (20)
- Translate Testing Recipes HOT 2
- reactjs - Hi Please help me to add row dynamically when the user clicks add row. HOT 1
- Translate 2016-03-07-react-v15-rc1
- [New] Tradução Concurrent Mode e Release Channels HOT 16
- Link da página Glossário de Termos React na seção JSX HOT 3
- Traduzir nova pagina de Equipe HOT 1
- Error translating documentation
- Translate 2020-09-22-introducing-the-new-jsx-transform.md
- Translate 2020-10-20-react-v17.md HOT 1
- Translate legacy-event-pooling.md
- Andamento da tradução HOT 4
- Translation Error (useCallback) - PT-BR HOT 1
- Traduzir content/blog/2021-06-08-the-plan-for-react-18.md HOT 2
- Fix typo in dangerouslySetInnerHTML translation. HOT 1
- Tradução da documentação para pt-br (Translation Progress) HOT 121
- Como contribuir na tradução? HOT 5
- I hope I can join this community.
- Diretrizes ao traduzir "state" precisam ser adicionadas ao repositório HOT 1
- Tradução do termo sandbox(trechos de códigos de examplo dentro da documentação) HOT 1
- Tradução do termo "top level" para raíz
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pt-br.react.dev.