[Translation][Spanish] Node.js, from English (1100 words) [N'14]

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 serve 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 working properties as a medium for bringing to reality countless creations that can be as good as Node itself. Imagination (and Java) is the 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 13th contribution to Node.js as a translator. For this collaboration, I continued my previous work on CHANGELOGS_ARCHIVE.md file, translating Node's changelogs of versions between 0.3.0 and 0.1.90.

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 programs, new functions, corrected errors and fixed bugs. To sum up: every single feature that started being applied in each version must be specified and described in this registry. The objective of that is providing a timeline of the development of the project and, by doing so, helping programmers to check any detail they need to understand the way it came to be what it is and make it better in the future.

I can refer to one of the logs I translated to illustrate the dynamics of the changelog. This one is from Version 0.1.91:

This entry introduced the update of Chrome V8 to its version 2.2.3.1. V8 is an open-source Javascript engine created and released by Google in 2008 as an integrated tool of its web browser Google Chrome. To the date, it runs in a great number of operating systems, as Microsoft Windows, Mac OS X, Linux, FreeBSD, Android, Google Chrome OS, webOS and BlackBerry 10. It compiles, interprets, executes and optimizes JavaScript code within the machine code... And having all this functions in one simple engine stands as an astounding feature! This engine is programmed in C++ and it is the base of all Node's platform. Since its creation, the work on Node has gone side to side with the development of V8; usually, all versions of Node include an upgrade in the code engine. Developers are aware of keeping it up to date, in order to let users enjoy all the tools V8 offers. At the moment this commit was written, version 2.2.3.1 was the latest. The V8's version being run now is 7.0 (released on October 15th).

You can check some references here for more information about this resource:

• https://v8.dev/
• https://github.com/v8/v8
• https://en.wikipedia.org/wiki/Chrome_V8
• https://medium.freecodecamp.org/understanding-the-core-of-nodejs-the-powerful-chrome-v8-engine-79e7eb8af964

V8's logo

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:

Add destroy methods to HTTP messages

Spanish:

Añadir métodos de destrucción para los mensajes HTTP

• Work example #02:

English:

Switch order of arguments for Buffer.write (Blake Mizerany)

Spanish:

Intercambiar orden de los argumentos para Buffer.write (Blake Mizerany)

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

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.

Proof of Authorship

This translation was made between October 22nd and 23rd, 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].