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.

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

Tradução das Sidebar #663

Merged
merged 34 commits into from
May 10, 2023
Merged

Tradução das Sidebar #663

merged 34 commits into from
May 10, 2023

Conversation

emersonbroga
Copy link
Contributor

  • SidebarHome
  • SidebarLearn
  • SidebarBlog
  • SidebarCommunity
  • SidebarReference

Copy link
Contributor

@jotaRenan jotaRenan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oi Emerson, muito obrigado pela sua maravilhosa tradução nessa contribuição.

Comentei algumas sugestões: a maioria envolve adequar letras maiúsculas para que sigam o estilo definido na documentação original. Em outros casos, sugeri manter nomes próprios do react em inglês. Houve apenas um caso em que havia um erro de digitação na tradução. Abç e vamos nessa!

src/sidebarCommunity.json Outdated Show resolved Hide resolved
src/sidebarCommunity.json Outdated Show resolved Hide resolved
src/sidebarHome.json Outdated Show resolved Hide resolved
"path": "/learn/managing-state"
},
{
"title": "Escape Hatches",
"title": "Escotilhas de escape",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Na minha tradução desse artigo, utilizei o termo "Saídas de emergência", por ser mais comum. Mas não tive certeza quanto à adequação dele. O que voce acha?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fiquei também confuso nessa parte, vou seguir sua sugestão de "Saídas de emergência", faz muito mais sentido que a tradução literal. Obrigado.

src/sidebarLearn.json Outdated Show resolved Hide resolved
src/sidebarLearn.json Outdated Show resolved Hide resolved
src/sidebarLearn.json Outdated Show resolved Hide resolved
src/sidebarLearn.json Outdated Show resolved Hide resolved
src/sidebarLearn.json Outdated Show resolved Hide resolved
src/sidebarLearn.json Outdated Show resolved Hide resolved
emersonbroga and others added 2 commits April 26, 2023 10:05
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
emersonbroga and others added 7 commits April 26, 2023 10:06
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
emersonbroga and others added 12 commits April 26, 2023 10:09
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
emersonbroga and others added 6 commits April 26, 2023 10:13
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
Co-authored-by: João Pedro Renan <[email protected]>
@emersonbroga
Copy link
Contributor Author

Obrigado @jotaRenan pelo review.

},
{
"title": "Describing the UI",
"title": "Descrevendo a IU",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Será que não seria bacana deixar essa parte como "Descrevendo a UI" ao invés de IU?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Será que não seria bacana deixar essa parte como "Descrevendo a UI" ao invés de IU?

@emersonbroga Eu traduzi esse termo como Construindo a UI neste PR #660 .

A ideia geral deste tópico é explicar como estruturar a UI usando States e Componentes. A palavra inglesa Describing tem esse sentido, mas a palavra brasileira Descrevendo não tem. Acredito que faz mais sentido manter Construindo a UI ou algum termo semelhante.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Também acho que manter "UI" não traz prejuízo à tradução. Quanto à "Construindo/descrevendo", não tenho opinião.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

também gosto do UI

"path": "/learn/you-might-not-need-an-effect"
},
{
"title": "Lifecycle of Reactive Effects",
"title": "Ciclo de Vida dos Efeitos Reativos",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Qual padrão seria ideal seguirmos? Alguns termos técnicos me parecem ideal deixar sem a tradução, padronizando.
"Ciclo de Vida dos Reactive Effects" o que vocês acham?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eu sugiro traduzir a palavra Reactive, mas não a Effects.

Copy link
Contributor Author

@emersonbroga emersonbroga Apr 26, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seria então "Ciclo de Vida dos Effects Reativos" ?

(commit emersonbroga@e03512f)

"path": "/learn/importing-and-exporting-components"
},
{
"title": "Writing Markup with JSX",
"title": "Escrevendo marcação com JSX",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Traduzi a palavra markup como tag neste PR: #660

Sugiro -> "Escrevendo Tags com JSX"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@natrodrigo, para facilitar a vida do autor da PR ao sugerir alterações simples, vc pode clicar nesse botao para que a UI do github possibilite o merge da sugestao com apenas 1 clique 👍 👍 👍 .
image

"path": "/learn/javascript-in-jsx-with-curly-braces"
},
{
"title": "Passing Props to a Component",
"title": "Passando Props a um Componente",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sugiro

"Passando Props para um Componente"

"tags": [],
"path": "/learn/describing-the-ui",
"routes": [
{
"title": "Your First Component",
"title": "Seu primeiro Componente",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sugiro

"Seu Primeiro Componente"

Para manter o padrão de caixa alta do original.

"path": "/learn/rendering-lists"
},
{
"title": "Keeping Components Pure",
"title": "Mantendo seu Componente Puro",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sugiro manter o plural do original:

"Mantendo seus Componentes Puros"

Copy link
Member

@jhonmike jhonmike left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ficou da hora 👏, apenas 2 sugestões mesmo, vê o que acha!

@@ -4,7 +4,7 @@
"routes": [
{
"hasSectionHeader": true,
"sectionHeader": "STAY INFORMED"
"sectionHeader": "MANTENHA-SE INFORMADO"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Será se não é o caso de traduzir os titulos abaixo?

},
{
"title": "Describing the UI",
"title": "Descrevendo a IU",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

também gosto do UI

@jhonmike jhonmike added 🌐 translated Translation is completed for this page needs author response Changes requested needing author's input labels Apr 28, 2023
Copy link
Member

@jhonmike jhonmike left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vamos dar merge @emersonbroga, os ajustes vemos no futuro

@github-actions
Copy link

Size changes

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Three Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load
/404 76.2 KB (🟢 -403 B) 169.83 KB
/500 76.19 KB (🟢 -403 B) 169.82 KB
/[[...markdownPath]] 77.72 KB (🟢 -299 B) 171.34 KB
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

@jhonmike jhonmike merged commit d4b73ee into reactjs:main May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs author response Changes requested needing author's input 🌐 translated Translation is completed for this page
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants