Glossary translation

[dmoralesm]

Hello all, I need some help here, there are some words that I don't feel comfortable to translate, because I'm from México and we are use to use these words as its in english.

Some words are:
re-render
arrow function
template literals
controlled component
uncontrolled component
props
state
camelcase
lowercase
callback
event handler

I need your opinion on what would be a suitable translation for these words.

Related with #1

[gariasf]

I personally think that these concepts can't and don't need to be translated. They are words that we lend from English and I've always seen them used in English, regardless of language.
For instance, camelcase has always been called camelcase, I don't think we have an equivalent word for that, and the literal translation wouldn't make sense. The same applies to most of those terms.

I must say that I believe they will be understood by most if not all of Spanish readers when looking at the docs.

However, here are some suggestions:

• lowercase -> minúscula (ending with s for plural)
• state -> estado (as in "estado del componente")
• props -> propiedades (given that "props" comes from "properties", but it can be abbreviated as props anyway)
• uncontrolled component -> componente descontrolado
• controlled component -> componente controlado
• re-render -> re-renderizado (as in "re-rendered") or re-renderizar (as in "to re-render")

The rest don't really make sense or can't be correctly translated into Spanish, IMO.

[ElRodrigote]

@gariasf just a minor correction:
props -> propiedades (the explanation you gave is 100% accurate).

And as Guillem said, there are some words that as far as I've heard, always are "spanishized", as "renderizado".

[gariasf]

@gariasf just a minor correction:
props -> propiedades (the explanation you gave is 100% accurate).

I missed that, thanks!

These are technical terms, take the word "string", it was mentioned on a different PR. It's not really translatable, a string has always been a string and any (or most of them) programmer knows what a string is, regardless of language.

[carburo]

Of course, all these terms sound familiar to us and we may be tempted to let them as is. This is not always the best solution as it may be confusing due to the abuse of mixing the two languages.
Here are my proposals for the terms:

• re-render -> Most of the time it's probably best to avoid the cacophony of rerenderizar and its derivatives with phrases like volver a renderizar (The correct spelling is rerenderizar not re-renderizar (See section 7 of this document about the 2010 Ortografía).
• arrow function -> función flecha (This is a term I've seen several times (MDN and Wikipedia use it) and it is a well-formed translation)
• template literals -> plantillas de cadena o plantillas de cadena de texto (as MDN). The translation of string to cadena or cadena de texto is widely used in many technical docs as well as the translation of template to plantilla.
• controlled component -> componente controlado
• uncontrolled component -> componente no controlado or componente descontrolado
• props -> props or propiedades
• state -> estado
• camelcase -> camelcase
• lowercase -> minúscula
• callback -> callback
• event handler -> manejador de eventos (It is a translation I've seen used several times in technical documentation and it sounds natural in Spanish.)

Last, but not least. I know many people use librería as a translation of library. I already gave my opinion in one PR #3. I am goin to repeat it:

Although the use of “librería” as a translation for “library” is adopted by many people is also discouraged by others. I think the position of the Royal Academy on this matter should be considered.
Also, “biblioteca” is the preferred term by many official docs, check out:

• https://developer.android.com/topic/libraries/support-library/?hl=es-419
• https://developers.facebook.com/docs/reference/php?locale=es_ES

[gariasf]

Of course, all these terms sound familiar to us and we may be tempted to let them as is. This is not always the best solution as it may be confusing due to the abuse of mixing the two languages.
Here are my proposals for the terms:

• re-render -> Most of the time it's probably best to avoid the cacophony of rerenderizar and its derivatives with phrases like volver a renderizar (The correct spelling is rerenderizar not re-renderizar (See section 7 of this document about the 2010 Ortografía).
• arrow function -> función flecha (This is a term I've seen several times (MDN and Wikipedia use it) and it is a well-formed translation)
• template literals -> plantillas de cadena o plantillas de cadena de texto (as MDN). The translation of string to cadena or cadena de texto is widely used in many technical docs as well as the translation of template to plantilla.
• controlled component -> componente controlado
• uncontrolled component -> componente no controlado or componente descontrolado
• props -> props or propiedades
• state -> estado
• camelcase -> camelcase
• lowercase -> minúscula
• callback -> callback
• event handler -> manejador de eventos (It is a translation I've seen used several times in technical documentation and it sounds natural in Spanish.)

Last, but not least. I know many people use librería as a translation of library. I already gave my opinion in one PR #3. I am goin to repeat it:

Although the use of “librería” as a translation for “library” is adopted by many people is also discouraged by others. I think the position of the Royal Academy on this matter should be considered.
Also, “biblioteca” is the preferred term by many official docs, check out:

• https://developer.android.com/topic/libraries/support-library/?hl=es-419
• https://developers.facebook.com/docs/reference/php?locale=es_ES

Thanks @carburo.

[tesseralis]

@dmoralesm how is this going? Could you respond to the changes people have requested?

[dmoralesm]

Hey @carburo @alejandronanez, I updated this PR. Can you take a look? Thanks.

[alejandronanez]

It still feels weird to me that we translate most of the technical terms to Spanish template literals or arrow functions for example, but if that's what everybody agreed on, I'm ok with that.

We can revisit after the first release and see what other teams are doing!

Sounds good @tesseralis @dmoralesm @carburo ?

[dmoralesm]

It still feels weird to me that we translate most of the technical terms to Spanish template literals or arrow functions for example, but if that's what everybody agreed on, I'm ok with that.

We can revisit after the first release and see what other teams are doing!

Sounds good @tesseralis @dmoralesm @carburo ?

Sounds good to me. I'm also inclined to not translate them, but some people refered to MDN translations and other sites too where the use this translations.

[tesseralis]

Haha, I don't really have a stake in what sounds better in Spanish, as long as you're following the glossary consistently.