Glossary and Style Guide about pt-br.react.dev HOT 90 CLOSED

also applies for "state" for example i.e. "mudança de estado (state)". it's important to educate non-English readers about the word meaning without losing context

from pt-br.react.dev.

I think that bind needs to be translated, something link vincular, do you agree with that @eduardomoroni? we can put on the suggested list

Agree w/ @eduardomoroni many of video tutorials in portuguese teachs as 'bind'. I think unnecessary translate this word to portuguese.

from pt-br.react.dev.

Stream is a very common term in computing and holds a lot of meaning which might easily get lost during translation.

I would say that this should not be translated, my 2 cents 💰

from pt-br.react.dev.

Hey everybody! Thanks for all the contributions and suggestions.

Defining common translations in a single issue makes it harder to keep track in the long term and also to reach consistency throughout our content.

We are starting to version control our Glossary (see #46) so if you would like to ask for suggestions on how to translate a given term please open an Issue for it. This will help to focus the discussion for each term while also helping to keep track when/how each term was added to our Glossary since we can link each issue to its own Pull Request.

Thanks again!

from pt-br.react.dev.

I want your opinions on this one: the verb log, what do you think is the best option to translate this one? @glaucia86, @eduardomoroni?

I don't think this has a good translation (mainly if you consider its etymology as a reference to wooden logs). My suggestion is that we treat it as a noun, like "adicionar ao log", "remover do log", etc.

from pt-br.react.dev.

Yeah, I was thinking about that, but when we have something like "logs SOMETHING to the console". Which expression can I use to refer to that? I mean, what's the best option?

I was thinking about that when I was trying to translate print. Feels really weird to say imprimir even if the translation is pretty accurate (feels like people always say printar). Maybe we can unify both cases and say imprimir no console (the least bad translation I can think of).

from pt-br.react.dev.

Yeah, I was thinking about two options:

• escrever no console
• imprimir no console

from pt-br.react.dev.

I'll include log as a word unnecessary to translate

from pt-br.react.dev.

lol thanks @WendellAdriel

from pt-br.react.dev.

Theres any translation sugested for build? like in build steps, I should use etapas de build or etapas de construção?

I'd say the usage of build among PT-BR devs has become ubiquitous enough to not need translation (Edit: definitely could use more input from other devs though)

from pt-br.react.dev.

We have these two terms for components that would be great have in the glossary too:

• stateless components: componentes sem estado
• stateful components componentes com estado

from pt-br.react.dev.

are we supposed to translate default?

I'm trying to think of a good fit for it but neither padrão or predefinido do seem right.

I would keep it as default.

from pt-br.react.dev.

@moiseshilario @michellocana This is entirely personal but I believe userland could be translated as comunidade, at least in your example, since it usually refers to open-source packages written by the community.

In general we resist adding features that can be implemented in userland.

[...] que podem ser implementadas pela comunidade.

from pt-br.react.dev.

If you take a look at this translation proposal #3, sometimes it makes sense to not translate bind, because you might be referencing the bind method.
But we translate bound and translate only the past tense, then the reading can be confusing for those who don't know what bind means.

I don't know what is the better way to approach honestly, but I think that making use of:

os métodos de classe que não foram bind

instead of

os métodos de classe que não foram vinculados

Can be friendlier for those with no knowledge of English and/or JS. Because people will understand that we're talking about the bind method.

from pt-br.react.dev.

I understood the issue. I finished reading the translation proposal now and yeah, it can be confusing. I think that bind can be a word that we won't translate.

We can also use os métodos de classe que não foram feito bind.

I'll add that to the glossary

from pt-br.react.dev.

I'm of the opinion that we should use 'imprimir no console'.

And what about markup? As in 'render components to static markup'.
I was thinking: 'renderizar componentes para markup estático'

from pt-br.react.dev.

words that are also method names such as "bind", "call", "apply" should be translated along the original inside parenthesis such as ... conectar (bind) or similar.

hard to tell without context but as PRs start to come using these terms we can refine the glossary

from pt-br.react.dev.

not sure if it was mentioned somewhere else but we should consider not translating code blocks (comments allowed). I'm better if we do not but don't have a strong opinion. what do you all think?

from pt-br.react.dev.

It's the first item on the issue @cezaraugusto!!! 😉

from pt-br.react.dev.

@WendellAdriel something like this

The Effect Hook lets you perform side effects in function components

O Hook de efeito permite você realizar efeitos colaterais em componentes funcionais

O Hook effect permite você realizar side effects em componentes funcionais

from pt-br.react.dev.

If you consider that "side effects" come from the concept of idempotence (idempotência), I guess "efeitos colaterais" is applicable.

from pt-br.react.dev.

How can we translate single-page apps?

I think this can't be translated because it's a proper noun and also has the acronym SPA.

from pt-br.react.dev.

Theres any translation sugested for build? like in build steps, I should use etapas de build or etapas de construção?

For me: Etapas de Build

from pt-br.react.dev.

What is the best way to translate "subclassing"?

React components can be defined by subclassing React.Component or React.PureComponent.

I'm currently thinking on

Componentes React podem ser definidos ao extender React.Component ou React.PureComponent.

from pt-br.react.dev.

I'm translating the CodeEditor file but we have the following scenario:
consider adding reactjs.org to the whitelist so the live code examples will work.
In my opinion live code is another therm that we shouldn't translate.

from pt-br.react.dev.

"codebase" = "base de código" or "código-base" ?

+1 "código-base"

from pt-br.react.dev.

I'm not sure how to translate Composing Components?

Could you give us a little more context?

It's this section in Components and Props: https://reactjs.org/docs/components-and-props.html#composing-components

It's about using the same component but with different props.

I would go with "Compondo componentes" to keep coherence with the next section "Extraindo componentes"

from pt-br.react.dev.

Should we translate high order component? Don't think so...

We should check how classic authors of Functional Programming were translated. I did a quick check in Wikipedia for Higher-order function but there's no Portuguese translation albeit all the available translations of the article were pretty literal, the Spanish one being what could be the most accurate, something like "Função de ordem superior" --> "Componente de ordem superior".

But it's a bit boring I guess, too formal... hahaha

from pt-br.react.dev.

"codebase" = "base de código" or "código-base" ?

I think that better translates to "base de código".

"Código-base" would be something like "base code"?

In context it even makes more sense:

Vou procurar na minha base de código.

Vou procurar no meu código-base.

from pt-br.react.dev.

Guys, are you really translating Context (the name of Context api) to "Contexto"?

Since props is never translated to "propiedades", I don't think it makes any sense to describe Context API using the pt-BR word "Contexto". It could confuse readers about what's Context (the api) and "Contexto" at all.

That's a good point. I would stick with Context.

from pt-br.react.dev.

is bind one of them?

from pt-br.react.dev.

I think that bind needs to be translated, something link vincular, do you agree with that @eduardomoroni? we can put on the suggested list

from pt-br.react.dev.

I want your opinions on this one: the verb log, what do you think is the best option to translate this one? @glaucia86, @eduardomoroni?

from pt-br.react.dev.

I think we don't need to translate log as well, I remember the first time someone translated Arcabouço in a talk, It took me like 5min to understand that they were talking about a framework.
I someone doesn't understand log, they could easily google for it and figure out for themselves.

from pt-br.react.dev.

Yeah, I was thinking about that, but when we have something like "logs SOMETHING to the console". Which expression can I use to refer to that? I mean, what's the best option?

from pt-br.react.dev.

'siblings' as well.
e.g. 'Keys used within arrays should be unique among their siblings'

Possible options:

• 'elementos irmãos'
  or
• 'items irmãos'

from pt-br.react.dev.

words that are also method names such as "bind", "call", "apply" should be translated along the original inside parenthesis such as ... conectar (bind) or similar.

Yeah, I liked this idea.

from pt-br.react.dev.

I want your opinions on this one: the verb log, what do you think is the best option to translate this one? @glaucia86, @eduardomoroni?

I don't think this has a good translation (mainly if you consider its etymology as a reference to wooden logs). My suggestion is that we treat it as a noun, like "adicionar ao log", "remover do log", etc.

Agree! Do not need a translation to log word

from pt-br.react.dev.

So, when translating something that relates to the React word, we need to define here a standard and stick to it, should we use:

• React
• a React
• o React

After defined, we need to include that on the Style Guide above.

cc: @glaucia86 @cezaraugusto @fjoshuajr

from pt-br.react.dev.

"o React" sounds good

from pt-br.react.dev.

So, when translating something that relates to the React word, we need to define here a standard and stick to it, should we use:

• React
• a React
• o React

After defined, we need to include that on the Style Guide above.

cc: @glaucia86 @cezaraugusto @fjoshuajr

• o React

from pt-br.react.dev.

Great, I'll push this to the Style Guide and also fix my own translations, LOL!!! 🤣🤣🤣

from pt-br.react.dev.

Effect as well?

from pt-br.react.dev.

@thadeu im not translating effects and side effects

from pt-br.react.dev.

I don't see any cases that we can't translate effect, I think that's a common word

from pt-br.react.dev.

Huum, I thought that because its a common word like state and such

from pt-br.react.dev.

How can we translate single-page apps?

from pt-br.react.dev.

What do you guys think about mock? I'd say this is a technical term and we shouldn't translate it, but if we do, the closest I can think of would be imitação.

from pt-br.react.dev.

I think that's better to not translate mock, I'll add it to the list

from pt-br.react.dev.

Does toolchain fit into the do-not-translate category? Or is the translation cadeia de ferramentas commonly used enough to merit a case?

from pt-br.react.dev.

Theres any translation sugested for build? like in build steps, I should use etapas de build or etapas de construção?

from pt-br.react.dev.

What about tags? I would say to leave this in english

from pt-br.react.dev.

I think the term "function components" should be translated as "componentes função" or "componentes de função", since it's different from "functional components".

from pt-br.react.dev.

I think that's better to not translate mock, I'll add it to the list

Can add spy on the list too.

from pt-br.react.dev.

are we supposed to translate default?

I'm trying to think of a good fit for it but neither padrão or predefinido do seem right.

from pt-br.react.dev.

Also it's important to notice that the term has changed from "functional component" to "function component", see here:
reactjs/react.dev#863

from pt-br.react.dev.

@WendellAdriel could you please add build to non-translated words?

from pt-br.react.dev.

What about stream guys?
e.g. The stream returned from this method will return a byte stream encoded in utf-8.

from pt-br.react.dev.

What about stream guys?
e.g. The stream returned from this method will return a byte stream encoded in utf-8.

I would go for Este método retona uma bytestream codificada em utf-8

from pt-br.react.dev.

At React pools events, what do you think would be a good translation for that?

from pt-br.react.dev.

I'm not sure how to translate Composing Components?

from pt-br.react.dev.

I'm not sure how to translate Composing Components?

Could you give us a little more context?

from pt-br.react.dev.

I'm not sure how to translate Composing Components?

Could you give us a little more context?

It's this section in Components and Props: https://reactjs.org/docs/components-and-props.html#composing-components

It's about using the same component but with different props.

from pt-br.react.dev.

from pt-br.react.dev.

props or propriedades?

e.g:

To modify a child, you re-render it with new props.

Para modificar um componente filho, você terá que re-renderizá-lo com as novas props.

Should I use props ou propriedades?

from pt-br.react.dev.

props or propriedades?

e.g:

To modify a child, you re-render it with new props.

Para modificar um componente filho, você terá que re-renderizá-lo com as novas props.

Should I use props ou propriedades?

I would stick with props since the full term (properties) is never used in English.

from pt-br.react.dev.

Probably you can translate as "Compondo Componentes" or "Componentes Compostos". It may depend on the context.
…

I agree with "Compondo Componentes"

from pt-br.react.dev.

Theres any translation sugested for build? like in build steps, I should use etapas de build or etapas de construção?

For me: Etapas de Build

I think Etapas do Build also is a valid translation depending on the context. Because steps are a process and these steps are towards to the Process.

from pt-br.react.dev.

And how about "wrapped"?

React components can also be defined as functions which can be wrapped

Componentes React também podem ser definidos como funções que podem ser envoltas

from pt-br.react.dev.

What is the best way to translate "subclassing"?

React components can be defined by subclassing React.Component or React.PureComponent.

I'm currently thinking on

Componentes React podem ser definidos ao extender React.Component ou React.PureComponent.

It's written estender

from pt-br.react.dev.

And how about "wrapped"?

React components can also be defined as functions which can be wrapped

Componentes React também podem ser definidos como funções que podem ser envoltas

Perhaps "embrulhadas"?

from pt-br.react.dev.

What is the best way to translate "subclassing"?

React components can be defined by subclassing React.Component or React.PureComponent.

I'm currently thinking on

Componentes React podem ser definidos ao extender React.Component ou React.PureComponent.

It's written estender

Whoops 🤕

from pt-br.react.dev.

Should we translate the term lifecycle?

Examples:

Hooks let you organize side effects in a component by what pieces are related (such as adding and removing a subscription), rather than forcing a split based on lifecycle methods.

We'll talk more about how this compares to class lifecycles in [Using the Effect Hook]

I don't think so.

from pt-br.react.dev.

Guys,
Italics vs Plain text for non-Translatable words?

from pt-br.react.dev.

Should we translate high order component? Don't think so...

from pt-br.react.dev.

"codebase" = "base de código" or "código-base" ?

from pt-br.react.dev.

"código-base" then

from pt-br.react.dev.

Hey guys,
What about Error Boundaries? It's not listed above but I haven't seen anybody translating it in blog posts. Should we leave it in English or translate it anyway? What do you think? 🤔

from pt-br.react.dev.

Hey guys,
What about Error Boundaries? It's not listed above but I haven't seen anybody translating it in blog posts. Should we leave it in English or translate it anyway? What do you think? 🤔

For the sake of searchability, I don't think this kind of terms that almost compound a noun should be translated. It will be easier in the future for a user willing to know how to use error boudaries to search for this name than for "Limites de Erro" or "Fronteiras de Erro".

I've just translated the page for "Error Decoder" but I think that's different for not being a "feature" per se, it's rather just a description of a behaviour.

Makes sense?

from pt-br.react.dev.

Makes total sense @halian-vilela ! Searchability is a great argument for that. 👍

Thank you!

from pt-br.react.dev.

Should we translate the term lifecycle?

Examples:

Hooks let you organize side effects in a component by what pieces are related (such as adding and removing a subscription), rather than forcing a split based on lifecycle methods.

We'll talk more about how this compares to class lifecycles in [Using the Effect Hook]

I don't think so.

I think that it should be translated to:
Lifecycle methods = Métodos do Ciclo de Vida
Class lifecycles = Ciclos de vida da classe

from pt-br.react.dev.

is bug === erro === error?

from pt-br.react.dev.

Hey @eduardomoroni

is bug === erro === error?

I think semantically yes, but the context where they are used are pretty different.

bug: something unpredicted, not obvious or easy to spot, generally in the source code of the main codebase or associated libraries which prevents the code from running as expected

error: the result of a bug, which can be seem by an error message or something similar

That's raises the doubt if bug shouldn't be considered as "doesn't need translation".

What do you guys think?

from pt-br.react.dev.

Guys, are you really translating Context (the name of Context api) to "Contexto"?

Since props is never translated to "propiedades", I don't think it makes any sense to describe Context API using the pt-BR word "Contexto". It could confuse readers about what's Context (the api) and "Contexto" at all.

from pt-br.react.dev.

hi people,
what do you think is the best translation for "opt-in feature"?

from pt-br.react.dev.

hi people,
what do you think is the best translation for "opt-in feature"?

it depends of the context, but maybe "funcionalidade opcional"?

from pt-br.react.dev.

what about

[...] ReactDOM.render() does not modify the container node

should we use "nodo contêiner" or "elemento contêiner"?

from pt-br.react.dev.

How do you guys would translate "userland" ?

from pt-br.react.dev.

How do you guys would translate "userland" ?

@moiseshilario, if the phrase below is the one you are translating,

In general we resist adding features that can be implemented in userland.

i would translate to something like "[...] que podem ser implementadas do lado do usuário"

from pt-br.react.dev.

Hi! Should/How should we translate:

• Warning article titles
  • e.g "Refs Must Have Owner Warning" (I translated it as "Aviso de Refs Precisam Ter um Dono")
  • Another approach would be to leave them untranslated.
  • Or meet it halfway (something like "Aviso 'Refs Must Have Owner'"
• Hyperlinks for specific sections
  • e.g: #strings-refs-outside-the-render-method in refs-must-have-owner (My approach was to leave it as is)
• Terms like ref (I left as is, too)

from pt-br.react.dev.