[Translation][Spanish] Node.js, from English (1258 words) [N'22]

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 22nd 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 to two of the logs I translated to illustrate the dynamics of the changelog. Both of them belong to the documentation aspects of Node, and are included in the "Commits" section of the addressed file. The first one goes:

There are two important concepts involved in this log. Being able to understand it requires that we address each of them particularly.

The first one is "cluster". In Node, clusters usually refer to work stations, id est, virtual locations where methods are continuously running to complete tasks required by the user. They're called clusters since they operate in a similar way that computers connected by networks (a.k.a., clusters in a broader sense) do. These work stations are interconnected, so they can run conjoint tasks, but can behave independently one from another.

The second one is "worker". In programming, a worker is a method that is designed to complete an specific task. Like the workers in those old videos from the New York's skyscrapers, they each have a particular function that is vital for the successful completion of the projects the users have envisioned with Node.

men-on-girder-new-york-i7945.jpg

Image source

Once that is clarified, we can understand that this commit seeks to make easier to understand what happens in the clusters when no workers are active. If that is specified in the documentation of the project, users can make a much better use of the tools they got in it.

The second log I'll refer is this:

This commit is really simple, actually. It suggest the correction of a wrong merging process of two documents of Node. Merging documents doesn't just mean to copy-paste the contents of one into the other, but to make sure they both get unified in purpose, style and coherence. Once that is done, this document shall be useful for the users of Node.

An example of how smooth a document fusion should look like:

• 

GIF source

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

• https://whatis.techtarget.com/definition/cluster
• https://www.techopedia.com/definition/997/cluster-servers
• https://stackoverflow.com/questions/10300251/what-does-the-concept-of-worker-mean-in-programing
• https://en.wikipedia.org/wiki/Web_worker

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>3172e9c541</0>] - <1>build</1>: set file permissions before uploading (Rod Vagg) <2>#2623</2>

Spanish:

[<0>3172e9c541</0>] - <1>build</1>: establecer los permisos de archivo antes de la subida (Rod Vagg) <2>#2623</2>

• Work example #02:

English:

[<0>23579a5f4a</0>] - <1>doc</1>: add TSC meeting minutes 2015-08-12 (Rod Vagg) <2>#2438</2>

Spanish:

[<0>23579a5f4a</0>] - <1>doc</1>: añadir minutas de la reunión del TSC del 2015-08-12 (Rod Vagg) <2>#2438</2>

• Work example #03:

English:

[<0>c16e100593</0>] - <1>doc</1>: reorg release team to separate section (Rod Vagg) <2>#2455</2>

Spanish:

[<0>c16e100593</0>] - <1>doc</1>: reorganizar al equipo de lanzamiento en una sección separada (Rod Vagg) <2>#2455</2>

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: 1258.
• The total amount of words translated in this project (as a Da-vinci/Utopian translator) is: 24080.

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.

Proof of Authorship

This translation was made on November 27th, 2018. 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].