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

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 26th 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 are included in the "Commits" section of the addressed file's stable version 2.3.0. The first one goes:

There are two important concepts involved in this log and before we can understand it, we need to address them term by themselves.

The first one, already explained in a previous contribution, is cluster. I remind you that a cluster is an agglomeration of electronic devices connected through a common network, usually by Internet. By clustering various, users can execute common operations that use the resources of them all as a single unit, which is perfect for the multiple tasking Node requires. In this case, the referred operation is the closing of the servers where Node is operating.

• And what is a server?

That is the second concept we'll address (thank you for asking). A server is any physical or virtual instruments destined for managing networks. The connection of your personal device to the Internet requires the righteous establishment of a web server that dictates how the service provided by your local company will be managed. And that doesn't just apply for Internet connections, it goes to external particular devices, printers, file locations, databases and –BINGO!– clusters.

Image source

What this commit is proposing is that Node waits for the servers disconnection before closing the cluster that is interdependent with them. This is done to avoid any unwanted missing of data, problems with the execution of the whole program or unforeseen results that negatively affect the users experience with Node.

The second log I'll refer is this one:

We already talked about OpenSSL and FIPS... But we don't know what is the FIPS Mode and how it affects the execution of OpenSSL. The FIPS Mode of cryptographic programs is a special mode to run them. What it does is adapting the specificities and patterns of execution of any cryptographic features of a of program to be fully compliant with the latest version of the Federal Information Processing Standard. Experimental takes on the tasks said program has to execute would be, therefore, disabled for security reasons, and the only approaches accepted would be the ones that had been tested and proved to be safe.

Go FIPS, listen to Jimmy:

GIF source

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

• https://www.techopedia.com/definition/2282/server
• https://whatis.techtarget.com/definition/server
• https://en.wikipedia.org/wiki/Server_(computing)
• https://www.techopedia.com/definition/32061/clustering-analytics
• https://www.techopedia.com/definition/997/cluster-servers
• https://wiki.openssl.org/index.php/FIPS_mode_and_TLS
• https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/FIPS_Mode_-_an_explanation
• https://en.wikipedia.org/wiki/FIPS_140

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>81029c639a</0>] - <1>debugger</1>: improve ESRCH error message (Jackson Tian) <2>#1863</2>

Spanish:

[<0>81029c639a</0>] - <1>debugger</1>: mejorar el mensaje de error de ESRCH (Jackson Tian) <2>#1863</2>

• Work example #02:

English:

[<0>a79dece8ad</0>] - <1>docs</1>: add return value for sync fs functions (Tyler Anton) <2>#1770</2>

Spanish:

[<0>a79dece8ad</0>] - <1>docs</1>: añadir valor de retorno para funciones sincrónicas del sistema de archivos (Tyler Anton) <2>#1770</2>

• Work example #03:

English:

[<0>a251657058</0>] - <1>node</1>: mark promises as handled as soon as possible (Vladimir Kurchatkin) <2>#1952</2>

Spanish:

[<0>a251657058</0>] - <1>node</1>: marcar las promesas como manejadas tan pronto como sea posible (Vladimir Kurchatkin) <2>#1952</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: 1,764.
• The total amount of words translated in this project (as a Da-vinci/Utopian translator) is: 30,783.

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.

Proof of Authorship

This translation was made December 27th. 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].