Freecodecamp: [translation]: Update Spanish translations for contributing documentations

Created on 11 Oct 2018  ·  27Comments  ·  Source: freeCodeCamp/freeCodeCamp

Update the following in Spanish from their English version available in /docs directory:

  • [ ] [/docs/spanish/CONTRIBUTING.md](https://github.com/freeCodeCamp/freeCodeCamp/tree/master/docs/spanish/CONTRIBUTING.md) from its english version at /CONTRIBUTING.md

  • [ ] [/docs/spanish/README.md](https://github.com/freeCodeCamp/freeCodeCamp/tree/master/docs/spanish/README.md) from its english version at /docs/README.md

  • [ ] [/docs/spanish/how-to-catch-outgoing-emails-locally.md](https://github.com/freeCodeCamp/freeCodeCamp/tree/master/docs/spanish/how-to-catch-outgoing-emails-locally.md) from its english version at /docs/how-to-catch-outgoing-emails-locally.md

  • [ ] [/docs/spanish/how-to-setup-freecodecamp-locally.md](https://github.com/freeCodeCamp/freeCodeCamp/tree/master/docs/spanish/how-to-setup-freecodecamp-locally.md) from its english version at /docs/how-to-setup-freecodecamp-locally.md

  • [ ] [/docs/spanish/how-to-work-on-coding-challenges.md](https://github.com/freeCodeCamp/freeCodeCamp/tree/master/docs/spanish/how-to-work-on-coding-challenges.md) from its english version at /docs/how-to-work-on-coding-challenges.md

  • [ ] [/docs/spanish/how-to-work-on-guide-articles.md](https://github.com/freeCodeCamp/freeCodeCamp/tree/master/docs/spanish/how-to-work-on-guide-articles.md) from its english version at /docs/how-to-work-on-guide-articles.md

Once you are ready please make a pull request, preferably one for each file.

When you make a PR for this particular issue, do not tag it with Closes #XXXXX instead just reference it with #XXXXX

help wanted

Most helpful comment

Hi there,
It would be good if checkboxes at the top are checked so we can see what is left to be translated.
Thanks

All 27 comments

Hey @raisedadead 👋!
How could I claim /docs/README.md so we don't double work? Thanks

Hi @luisbd 👋!

Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours.

Happy translating.

I just open a PR for /docs/README.md 👉 https://github.com/freeCodeCamp/freeCodeCamp/pull/18314

@luisbd thanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often

Happy contributing.

Done translating /docs/spanish/CONTRIBUTING.md! My PR is available at #18318!

Thanks for all you do, freeCodeCamp 😎 👍

I have sent a translation proposal for /docs/how-to-work-on-guide-articles.md. PR #18411

Hope it will help!

There is still work pending on this. When you make a PR for this particular issue, do not tag it with Closes #XXXXX instead just reference it with #XXXXX

Hello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-locally.md

Working on /docs/spanish/how-to-work-on-guide-articles.md

Hello, I've improved the CONTRIBUTING.md file #18684

Hello,

Improving docs/spanish/how-to-catch-outgoing-emails-locally.md

Hi, I'm improving docs/spanish/how-to-work-on-coding-challenges.md

Hi, can I help with /docs/spanish/how-to-setup-freecodecamp-locally.md?

Sorry, I opened a bad PR regarding README.md but already closed it. I found there was still an English part to be translated #21848

Hi! Is there any remaining documentation where I can help translate?

@MetCoder95 you can improve or fix redaction and spelling errors.

Hi there,
It would be good if checkboxes at the top are checked so we can see what is left to be translated.
Thanks

Where I can start helping?

@raisedadead sorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are _a total crap_ (Like #28692) .

I guess you opened a Pandora Box with your articule about HacktoberFest.

Hey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. #28207.

@MetCoder95 or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't added in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder😊

Hola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages.

In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal.

Another thing that could be specified in the guidelines is:

Challenges translations. Should they be translated?
Referrals to types and attributes (which need to be in English for proper coding). For example, type "date" not type "fecha".

If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it).

Hey @raisedadead I would like to know your thoughts about this.

Thanks to you all and happy coding!

@tomaspozo I agree that we should standardize around informal.

I agree with you that we should look out for words like "fecha" that have been accidentally translated during our automated translation process.

Hi all 👋

I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment.

What do people think about translating "array" as "arreglo"?

I think this is a big mistake that has been repeated since somebody made that bad translation many years ago.

As any Spanish speaker know, "arreglo" means "repair" (all definitions here, ESP), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way.

I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that "arreglo" was the (really bad) translation of "array". Then I could read the text as if I was reading an encoded message that had to be deciphered.

I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is "ristra".

According to the Spanish RAE dictionary:

  1. f. coloq. Conjunto de ciertas cosas colocadas unas tras otras.

Which basically means: "A group of things placed one after another"

They also share all the phonems in "array", with the adittion of /r/ (rolling r) and /t/ in "ristra".

I'm open to other candidates, but please, let's take "arreglo" out of the Spanish version. The word "array" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like "list", "function", "import", "scope", etc.

Hello guy,

I vote for yes, let’s do the change and I think will create a huge impact around of the world!

Please let me know if you have more question questions or concerns.

Andres Haro
Cell: (619) 534-3190
[email protected]

On Jan 30, 2019, at 14:20, Daniel González Reina notifications@github.com wrote:

Hi all 👋

I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment.

What do people think about translating "array" as "arreglo"?

I think this is a big mistake that has been repeated since somebody made that bad translation many years ago.

As any Spanish speaker know, "arreglo" means "repair" (all definitions here, ESP), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way.

I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that "arreglo" was the (really bad) translation of "array". Then I could read the text as if I was reading an encoded message that had to be deciphered.

I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is "ristra".

According to the Spanish RAE dictionary:

f. coloq. Conjunto de ciertas cosas colocadas unas tras otras.
Which basically means: "A group of things placed one after another"

They also share all the phonems in "array", with the adittion of /r/ (rolling r) and /t/ in "ristra".

I'm open to other candidates, but please, let's take "arreglo" out of the Spanish version. The word "array" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like "list", "function", "import", "scope", etc.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@dgrcode Thanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join gitter.im/freecodecamp/contributors if you need help getting set up 👍

There is still work pending on this. When you make a PR for this particular issue, do not tag it with Closes #XXXXX instead just reference it with #XXXXX

Thanks for working on the translations for the "Contributing to freeCodeCamp". Here on we are making contributing to translations for contribution docs ad hoc.

You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se.

You can raise a fresh issue if you find something incorrect in the existing docs.

Was this page helpful?
0 / 5 - 0 ratings