[OLD] Legacy Spanish Translation Progress about es.reactjs.org

[GiuMagnani]

I vote for tú, I don't think a library's documentation should be that formal.

[RamirezAlex]

Hi @alejandronanez @carburo @tesseralis and others: I think it is very important that we establish which form of second-person treatment we are going to use for consistency. Meaning, I have seen some contributors using tú others using vos and others including me using usted. :D

In my case I started using usted because I consider this formal documentation, thus I use formal treatment and it is more neutral. However, I feel Ok using other as soon as it is consistent through the entire translation. What do you think? Peace 👍

[alejandronanez]

Ok!

@karolincastano you got Api Reference > React
@semoal you got Api Reference > React.Component
@elyalvarado you got Api Reference > Test Renderer
@Darking360 you got Api Reference > ReactDOM

Please, let me know if that doesn't work for you!

[RamirezAlex]

I would like to work on Fragments :-)

[carburo]

Welcome, @RamirezAlex! I already assign you Fragments. @LuisRevillaM, @elyalvarado, and @ElRodrigote I already assign you the issues you mentioned. Remember not to open new issues for translations.

[alejandronanez]

Hello!

@florenciasilva you got FAQ: Passing Functions to Components
@RamirezAlex I assigned Optimizing Performance
@jvelezpo you got refs-must-have-owners, invalid-aria-prop, dont-call-proptypes. Once you're done with those 3, you can claim JSX in Depth if it is still available 👍
@Darking360 Refs and the DOM is yours

Thank you friends!!!

[gariasf]

Also what about text in block codes?

[
  {category: "Sporting Goods", price: "$49.99", stocked: true, name: "Football"},
  {category: "Sporting Goods", price: "$9.99", stocked: true, name: "Baseball"},
  {category: "Sporting Goods", price: "$29.99", stocked: false, name: "Basketball"},
  {category: "Electronics", price: "$99.99", stocked: true, name: "iPod Touch"},
  {category: "Electronics", price: "$399.99", stocked: false, name: "iPhone 5"},
  {category: "Electronics", price: "$199.99", stocked: true, name: "Nexus 7"}
];

That's also in Thinking in React, should I translate the categories and names? (when they are not direct product names) I read on the main issue they will be copied as if in the future they are modified on the original version, also since it's data it could be left as is as an example.

I would leave code as is with the exception of comments.

[alepaz]

Hi! Let me help with Integrating with Other Libraries

[sergiodxa]

@shmesa22 I'm not sure there is a good translation for that, the correct one would be llamar de vuelta, maybe paraphrasing it it could fit in the sentence, however callback is a word commonly used in Spanish communities too so it may be an option avoid translating it.

[sergiodxa]

who is going to create the glossary? what's the criteria?

[tesseralis]

We'll probably have a TRANSLATION folder with style-guide.md and other useful guides in there. Let me get that set up.

[tesseralis]

@sergiodxa @shmesa22 I added TRANSLATION.md as a source for translation information, including a style guide: https://github.com/reactjs/es.reactjs.org/blob/master/TRANSLATION.md. Feel free to edit and suggest style guide tips.

[to-var]

Hola!

I can help with Shallow Renderer 👌🏻

[karolincastano]

Hi, I’m an English to Spanish translator and I would like to help with the contributing page translation.

[alejandronanez]

@michaelcavallaro03, @GiuMagnani, @LuisRevillaM, @KevinGomezDev all set.

[ricardoerl]

I would like to help with Context

[jonathanpalma]

I'd like to help with Render Props

[carburo]

Thank you for your interest.. 🎉 Context goest to @ricardoerl & Render Props to @jonathanpalma. Please, do not open new issues for translations.

[simonhoyos]

@icarlossz, no worries. I haven't started working on it, I can take another one

[tesseralis]

@shmesa22 @EzequielMonforte are you able to edit the issue to add your name on it?

Never mind, seems like you can't. Can you create issues for the pages you would like to translate and assign yourselves?

[sergiodxa]

I would like to work in Thinking in React

[alejandronanez]

You got it @ElRodrigote #17

[EzequielMonforte]

I would like work on List and keys too #18

[marbiano]

Hi, I'd like to help translating Composition vs Inheritance.

[joelalejandro]

Hello! I'd love to help with Forms.

[sigfriedCub1990]

Hello there, I would like to help with Lifting State Up

[semoal]

Hello! I'd love to help with React, or just the next going step on the priority list.

[elyalvarado]

Hello, I'd love to take Test Renderer. I opened issue #24

[Darking360]

Greetings. I'd love to translate React.Component 💪

[escorponox]

Let me take the Using the Effect hook if it is still available

[alejandronanez]

Hello 👋 @Darking360 and @anyk1709, thanks for your interest!

I already assigned you the issues you mentioned! 👍

[elyalvarado]

Having already finished with #24, and it already merged, I'll like to work on Create a New React App. Opened issue #63 for it.

[LuisRevillaM]

I would like to translate Code-Splitting on Advanced Guides.

[elyalvarado]

Done with #63. The PR is #68 in case anyone wants to check/comment. @carburo @alejandronanez

I'll like to work on Forwarding Refs from Advanced Guides.

[GiuMagnani]

Done with Hooks at a Glance. The PR is #70 @dmoralesm, @carburo and @alejandronanez. I'd love to keep working on Component State and Styling and CSS from FAQ. Thanks!

[ElRodrigote]

Welcome, @RamirezAlex! I already assign you Fragments. @LuisRevillaM, @elyalvarado, and @ElRodrigote I already assign you the issues you mentioned. Remember not to open new issues for translations.

Thanks! Didn't know, sorry, won't happen again :)

[elyalvarado]

Done with Forwarding Refs. PR is #72 @dmoralesm, @carburo and @alejandronanez.

I'll like to work on Higher-Order Components

[alejandronanez]

Ok, friends, we have:

• @GiuMagnani, I assigned to you Component State. I didn't assign Styling and CSS to you just yet, we're trying to have 1 PR per person at the time, also someone might be interested in Styling and CSS while you work in Component State. Once you're done with Component State let us know and we can assign Styling and CSS (or any other) to you! 👍
• @elyalvarado you got Higher-Order Components
• @alepaz you got Integrating with Other Libraries

[GiuMagnani]

Thanks @alejandronanez, I just sent the PR for the Component State FAQ: #75. Let me know when I can take the Styling and CSS or another that is available. Thanks again!

[carburo]

@GiuMagnani. I already assign you Styling and CSS.

[RamirezAlex]

I open a PR #82 for Fragments to close issue #80
I would like to continue with Optimizing Performance

[Darking360]

Hey! I just finished the PR for the Getting Started page here: Getting Started PR 🚀

I'd love to continue with: Refs and the DOM if that's ok. Please let me know, and I'll probably start it tomorrow 💪

CC: @tesseralis @dmoralesm @carburo @alejandronanez

[simonhoyos]

I would like to work on Introducing JSX

[alejandronanez]

Hey @shmesa22, I updated the description with your name on it! Thanks for helping us! 👍

Introducing JSX is issue #7

Let us know if you have any questions!

[icarlossz]

Hey @shmesa22, I didn't see your comment and I started with that one. Sorry.

[EzequielMonforte]

Hi. I want to work on Components and Props

[simonhoyos]

I would like to work on Rendering Elements then

[simonhoyos]

Hi @tesseralis, I was able to create the issue, but not to assign it to me

[simonhoyos]

Hi everyone, any thoughts or any good translation for callback?

[simonhoyos]

Thank you @sergiodxa, that's what I was thinking. I left it like that.

Also, I would like to start working on handling events.

[tesseralis]

@shmesa22 Once it's done, we should have the glossary as a reference on how to translate common terms. @dmoralesm how is that progress going?

[simonhoyos]

@tesseralis any way we can add or recommend words for the glossary?

[tesseralis]

@shmesa22 The original English glossary or the Spanish version? The Spanish docs should just be translation of the English version.

@sergiodxa The "glossary" in question is the translation of the version in the English docs: https://reactjs.org/docs/glossary.html

Currently @dmoralesm is assigned to translate it but if it's not done soon we should hand over the work to someone else.

[dmoralesm]

@shmesa22 Once it's done, we should have the glossary as a reference on how to translate common terms. @dmoralesm how is that progress going?

I'm about to finish

[sergiodxa]

I mean "a reference on how to translate common terms" that glossary.

[simonhoyos]

Same here, I was thinking on some glossary on how to translate words like callback or camelCase

[sergiodxa]

mock too

[sergiodxa]

Or at least define what words not to translate because they are used as is in Spanish

[sergiodxa]

Great!

I have another question, what about links to external sites? In Thinking in React there is a link to a Wikipedia page which has a Spanish translation, should I change the link to the Spanish version? or keep the English one?

[tesseralis]

@sergiodxa that seems like a good idea, but I'll leave it to more experienced translators. We can also put our decision in the style guide!

[sergiodxa]

Also what about text in block codes?

[
  {category: "Sporting Goods", price: "$49.99", stocked: true, name: "Football"},
  {category: "Sporting Goods", price: "$9.99", stocked: true, name: "Baseball"},
  {category: "Sporting Goods", price: "$29.99", stocked: false, name: "Basketball"},
  {category: "Electronics", price: "$99.99", stocked: true, name: "iPod Touch"},
  {category: "Electronics", price: "$399.99", stocked: false, name: "iPhone 5"},
  {category: "Electronics", price: "$199.99", stocked: true, name: "Nexus 7"}
];

That's also in Thinking in React, should I translate the categories and names? (when they are not direct product names) I read on the main issue they will be copied as if in the future they are modified on the original version, also since it's data it could be left as is as an example.

[tesseralis]

@sergiodxa maybe reference translations in other sites/languages to see what they do? Or see if you can find style guides from other technical projects we can use as a base for ours.

[dmoralesm]

I would leave code as is with the exception of comments.

I agree with @gariasf

[dmoralesm]

@sergiodxa @shmesa22 I added TRANSLATION.md as a source for translation information, including a style guide: https://github.com/reactjs/es.reactjs.org/blob/master/TRANSLATION.md. Feel free to edit and suggest style guide tips.

@tesseralis I would like to create a list of words that we must avoid to translate, such as string or callback. Is TRANSLATION.md a proper place to do it?

[tesseralis]

@dmoralesm Yup!

[ElRodrigote]

Hi!

I would like to take Conditional Rendering

BTW: my first contribution ever outside my work :D

[icarlossz]

When I finish with introducing jsx I want to continue with lists and keys

[carburo]

Hi, I’m an English to Spanish translator and I would like to help with the contributing page translation.

@karolincastano Every help is welcome. Right now the style guide is basically a stub. Feel free to propose changes to it.

[KevinGomezDev]

Hey y'all, I would like to start with Hooks. Introducing Hooks

[LuisRevillaM]

I would love to help with the DOM elements section of the API Reference.

[GiuMagnani]

I'd love to help with the Hooks at a Glance translation.

[Cavallando]

I would love to help with, SyntheticEvent translation! Created issue #26, PR #29

[alejandronanez]

@icarlossz List and Keys has already been assigned to @EzequielMonforte.

#4 (comment)

If you're done with #8 (it says WIP still) you should grab another piece of documentation. 😄

[sergiodxa]

I created the PR for Thinking in React (#27)

Now I want to work in Hooks FAQ #28.

[ivandevp]

I would like to help with the Tutorial section.

[sigfriedCub1990]

Hi, I’m an English to Spanish translator and I would like to help with the contributing page translation.

@karolincastano Every help is welcome. Right now the style guide is basically a stub. Feel free to propose changes to it.

@carburo, dónde está Guaso? Saludos de un hermano cubano

[alejandronanez]

Hey man, @sergiodxa, all set!

@ivandevp, alright, assigned it to you!

[a13marquez]

Hi everyone, i'd love to help in any section

[devrchancay]

I want to translate ReactDOMServer 🤓

[Zitle-Nancy]

Hello ! I want to translate Home :)

[d4vsanchez]

Hi! I’d like to help translating the “Test utilities” section.

I've finished translating this section on #73.

[alejandronanez]

Thanks for your interest friends, welcome 🎉

@d4vsanchez, @devrchancay and @Zitle-Nancy you're all set ✌️

[alejandronanez]

@a13marquez, please, choose one, we have plenty of work to do! 😄

[a13marquez]

@alejandronanez I can take Using the State Hook and Using the Effect Hook

[EzequielMonforte]

I want to work on #31

[jvelezpo]

i will work on Hooks API Reference

[alejandronanez]

@a13marquez I assigned Using the state hook, I didn't assign Effect hook to you right away to give others the opportunity to work on it. Let us know when you're done with your issue so we can assign another translation to you!

@icarlossz I assigned Rules of hooks to you.

@EzequielMonforte you got Building your own hooks

@jvelezpo you got Hooks API reference

[jvelezpo]

• special-props (this one is very short thats why i am taking another file)
• unknown-prop

#69

[alejandronanez]

Special props and Unknown Props are assigned to you @jvelezpo

[angelitaooo]

I want to work in JS environment requirements please!

[alejandronanez]

You got it @angelitaooo

[Darking360]

Greetings 🚀

I just created a PR for ReactDOM here: ReactDOM translation

I'd love to keep helping, maybe I can help with the Getting Started 🙏 let me know, and I'll start it probably tonight 👍 @dmoralesm

Hey! I'd like to help with Add React to a Website

[ElRodrigote]

Hi, I'm finishing #17 and would like to take Accessibility as I've worked with that in my current job :)

[jesgarciamartinez]

Hi! I'd like to work on Error Boundaries

[jvelezpo]

Hello, i will work on

• refs-must-have-owner (this is a short file so i will take on other file)
• invalid-aria-prop (this one is also a short file)
• dont-call-proptypes

@alejandronanez One question i dont see legacy-properties but i see legacy-factories file, if this is a typo on the description of the issue, i can take on legacy-factories as well

#81

[jvelezpo]

I would like to work on

• JSX In Depth

[alejandronanez]

@jvelezpo thanks for your enthusiasm, but, please, take one issue at the time. It doesn't matter if they are small ones. Once you're done with one issue, we can assign you another.

That would make our work easier (as maintainers) and will let other people contribute with smaller issues too!

Thanks! 👍

[florenciasilva]

Hi! I would like to work on FAQ: Passing Functions to Components.
https://github.com/reactjs/es.reactjs.org/blob/master/content/docs/faq-functions.md

I just sent the PR for FAQ: Passing Functions to Components
I would like to continue with Virtual Dom and Internals when possible!
@alejandronanez @dmoralesm @carburo

[jvelezpo]

@alejandronanez done with refs-must-have-owners, invalid-aria-prop, dont-call-proptypes
on PR https://payfully.atlassian.net/browse/PF-711
i would like JSX in Depth if it is still available