[Translation][Spanish] Node.js, from English (1,070 words) [N'32]

Image source

Github Repository

https://github.com/nodejs/i18n

Project Details

By definition, Node.js is a Java Runtime Environment (JRE). But it is more than just that. While common JREs function as machine backups that allow users to smoothly run JavaScript on their browsers and applications, this open-source project functions as an app that manages Java code by itself. It's practical uses for developers are endless. It grants an extraordinarily versatile platform for designing code, programs, websites and other applications. And that isn't all: Node provides a virtual facility for testing the proper work of Java-driven programs and devices –and their planned updates–, helping to find bugs, solve errors, fix code and vastly improving their performance.

I believe all the amazing uses of Node are to be considered by themselves and I declare myself a fan of the project. But, besides, I support it for its functionality as a medium for bringing to reality countless creations that can be as good as Node itself. If you can dream it –and code it in JavaScript–, then your imagination is the only limit!The open translation of Node to thirty-three (33) languages proves the advantages of open-source projects when it comes to diversification of knowledge and worldwide spreading of useful tools.

Ahead, there is the link of the program's webpage:

https://nodejs.org

Contribution Specifications

Translation Overview

This is my 32nd contribution to Node.js as a translator. For this collaboration, I continued my previous work on the CHANGELOG_IOJS.md file, which –as its name indicates– contains the changelog of the io.js’ version of Node.

As I explained in my past translation reports, a changelog is a registry of all the changes made on determined project for each one of its versions. The files created for such purpose list modifications on internal components, substitutions of protocols, updates, deprecations, addition of supported tools, new functions, corrected errors and fixed bugs. In summary: every feature that first appeared or was removed in the program version being addressed must be specified and described in this registry. This is made with the purpose of providing a timeline of the development of the project and, by doing so, helping programmers to check any details they need to understand the way it came to be what it is and improve it in the future.

I'll refer two of the logs I translated to illustrate the dynamics of the changelog. Both of them are included in the "Commits" section of the addressed file's stable version 1.0.4. The first one goes:

There is one important expression here that requires understanding to address this commit. We're talking about what is a bad entry. In this context, a bad entry signifies a registry that doesn't fit within the set of logs that constitutes it. This is specially important in a list of this kind: changelogs rely on the exactitude of all their contents, as a source of documentation and planning for long term projects. This commit shows how meticulous users should be when they compromise to actively participate as contributors with Node.js. Removing the mentioned bad entry creates precision within the registry again.

Image source

The second log I'll refer is this one:

Two concepts to be addressed here. The first one is "copyright". Maybe you've heard this term a lot of times or seen this symbol © in some merchandising products, but do you really know what it means? It is a legal disposition that seeks to protect the creative work of the authors of all sorts of materials, considering such works as extension of their authors, products of their personalities and creative efforts. Plenty legislation has been developed around the world to give shape to this Western institution and this, further than fomenting global consensus on this matter, has only raised debate on which are its boundaries. In the last months, Internet has raised debate about a forthcoming European Union disposition of its general legislation's Article 13, also known as the "Meme Ban". I invite you to keep track of that story to understand better how copyrights work. Also, check this documental, is very informative and entertaining, and a great way to spend a home saturday night with some popcorn:

The second one is "boilerplate"... Boiler.... What?

GIF source

No...

Boilerplate refers to the section of an organization's documentation comprehended by all its legal dispositions. In this segment, all its fundamental information is stated and backed up in order to avoid frauds or suspicious statements that could lead to erroneous interpretation or use of the organization's intellectual work.

So...

Image source

Yup. That's better! Unless you are the guy from the picture, who apparently didn't read an important boilerplate and now has to face the consequences of it...

Now, we can understand this commit. What it states is the elimination of a segment of the Node.js organization's documentation referred to its intellectual rights on the program and its products.

Gif source

You can check some references here for more information about the previously addressed concepts:

• https://techterms.com/definition/copyright
• https://copyrightalliance.org/ca_faq_post/what-is-copyright
• https://en.wikipedia.org/wiki/Authors%27_rights
• http://www.businessdictionary.com/definition/boilerplate.html
• https://definitions.uslegal.com/b/boilerplate/
• https://en.wikipedia.org/wiki/Boilerplate_text

All changes included in each one of the versions of the project are formatted as pull-request commits. Id est, they are presented as very brief comments about the action that was suggested, are normally written with imperative verbs, and have a strict limitation on their number of characters (so even complex ideas are reduced to a small amount of words). These specifications made the translation of this document a challenge. However, it was satisfactorily achieved. As you will see in the examples below, the name of the developer who provided each log is often referred inside parenthesis at the end of it.

Image source

• Work example #01:

English:

<0>lookup()</0> now supports an <0>'all'</0> boolean option, default to <0>false</0> but when turned on will cause the method to return an array of <1>all</1> resolved names for an address, see, <2>#744</2> (@silverwind)

Spanish:

Ahora <0>lookup()</0> soporta una opción booleana <0>'all'</0>, que está establecida por defecto en <0>false</0>, pero al ser activada ocasiona que el método devuelva un array de <1>todos</1> los nombres resueltos para una dirección <2>#744</2> (@silverwind)

• Work example #02:

English:

New <0>Errors</0> page discussing JavaScript errors, V8 specifics, and io.js specific error details.

Spanish:

Nueva página de <0>Errores</0>, en la cual se discuten los errores de JavaScript, especificaciones de V8, y detalles de errores específicos de io.js.

• Work example #03:

English:

[<0>7604e6d</0>] - docs: add note about default padding in crypto (Calvin Metcalf)

Spanish:

[<0>7604e6d</0>] - docs: añadir nota sobre el relleno por defecto al documento de crypto (Calvin Metcalf)

Languages

This translation was made from English to Spanish.

I got plenty experience translating and proofreading this project as an Utopian contributor. I collaborate here as translator and Language Moderator of the Da-Vinci/Utopian Spanish translation team. Besides this project, I have experience translating and proofreading The Curious Expedition, Ancap-ch, Byteball Wiki, OroCrm and BiglyBT.

Word Count

• The amount of words translated in this contribution is: 1,070.

Note: This number is the result of subtracting the complete sum of non-translatable content to the word-count Crowdin has done for the period in which this contribution was done.

• The total amount of words translated in this project (as a Da-vinci/Utopian translator) is: 40,583*.

Previous Translations of the Project

• Contribution N'01. Submitted on September 13th, 2018.
• Contribution N'02. Submitted on September 15th, 2018.
• Contribution N'03. Submitted on September 17th, 2018.
• Contribution N'04. Submitted on September 19th, 2018.
• Contribution N'05. Submitted on September 21th, 2018.
• Contribution N'06. Submitted on September 22th, 2018.
• Contribution N'07. Submitted on September 23th, 2018.
• Contribution N'08. Submitted on October 1st, 2018.
• Contribution N'09. Submitted on October 8th, 2018.
• Contribution N'10. Submitted on October 14th, 2018.
• Contribution N'11. Submitted on October 15th, 2018.
• Contribution N'12. Submitted on October 18th, 2018.
• Contribution N'13. Submitted on October 21st, 2018.
• Contribution N'14. Submitted on October 24th, 2018.
• Contribution N'15. Submitted on October 27th, 2018.
• Contribution N'16. Submitted on October 31th, 2018.
• Contribution N'17. Submitted on November 3rd, 2018.
• Contribution N'18. Submitted on November 4th, 2018.
• Contribution N'19. Submitted on November 6th, 2018.
• Contribution N'20. Submitted on November 17th, 2018.
• Contribution N'21. Submitted on November 24th, 2018.
• Contribution N'22. Submitted on December 7th, 2018.
• Contribution N'23. Submitted on December 15th, 2018.
• Contribution N'24. Submitted on December 20th, 2018.
• Contribution N'25. Submitted on December 26th, 2018.
• Contribution N'26. Submitted on December 28th, 2018.
• Contribution N'27. Submitted on December 30th, 2018.
• Contribution N'28. Submitted on January 9th, 2019.
• Contribution N'29. Submitted on January 10th, 2019.
• Contribution N'30. Submitted on January 12th, 2019.
• Contribution N'31. Submitted on January 18th, 2019.

Proof of Authorship

This translation was made January 18th. You can check the translation record in my Crowdin account [here], the activity on the project's Crowdin [here] and a summary of recent additions to the project [here].
![Crowdin Profile.png](