[Translation][Spanish] Node.js, from English (1171 words) [N'17]

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 17th contribution to Node.js as a translator. For this collaboration, I started to work on CHANGELOG_V10.md file, continuing the translation begun by a fellow Da-Vinci/Utopian member. This document contains the commit logs of all accepted pull-requests related to Node's Version 10.

As I explained in my translation reports from CHANGELOGS_ARCHIVE.md, 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 one of the logs I translated to illustrate the dynamics of the changelog. This one belongs to the Semver-Major sub-section of the Commits.

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

The first one is "console". Consoles are virtual devices designed to allow users to communicate with a software by text input and output. They consist in an interface that displays messages that are readable and (with some specific knowledge!) understandable by users and a keyboard or text input mechanism connected to that interface. The use of these became relatively widespread in the late 50's thanks to IBM's advances and mass production of computer systems. Today, consoles are basic tools integrated to practically every operating systems.

Fun fact!: The classic Matrix screen full of green code... That thing... Yes! It is a console, a very complex one.

GIF source

The other term we need to define is "test". In computer science, unit tests (referred in this document just as "tests") are processes conducted by users to make sure all components of a determined element of a software run the way they should. Allowing the independent coding that represents the element being checked as input, tests imitate its normal run conditions and generate an output that is readable by users. These outputs describe all layers of functionality of the tested component and give hints to the developers about which parts of it, if any, must be modified for a suitable use. If tests are not taken seriously, bad consequences are inevitable. In the following GIF, the passengers represent developers who said: "Man... We're too smart to follow the recommendations of the test... Blah... Blah... Blah... We're too cool for them... Blah... Blah.. Blah..."; the car is the software they wanna run ignoring the aforementioned test; and the collapse... Well... The collapse is a literal collapse of that software.

GIF source

Knowing these concepts, the comprehension of the quoted entry becomes attainable. This commit specifies the addition of a test designed for the standard console of Node.js. With this inclusion, collaborators are now one step closer to achieve their goal of making Node error-safe, at the same time they will surely get suggestions from this new test about how to improve it's performance.

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

• https://www.webopedia.com/TERM/C/console.html
• https://en.wikipedia.org/wiki/System_console
• https://www.quora.com/What-is-a-console-in-programming
• https://searchsoftwarequality.techtarget.com/definition/unit-testing
• http://softwaretestingfundamentals.com/unit-testing/
• https://en.wikipedia.org/wiki/Unit_testing

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 (THE WHOLE FOLDER, YES!). 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>3e0d40d4af</0>] - <1>(SEMVER-MAJOR)</1> <1>test</1>: add info option to common.expectsError (Joyee Cheung) <2>#19514</2>

Spanish:

[<0>3e0d40d4af</0>] - <1>(SEMVER-MAJOR)</1> <1>test</1>: añadir opción de información a common.expectsError (Joyee Cheung) <2>#19514</2>

• Work example #02:

English:

[<0>9b8e1c2e4f</0>] - <1>(SEMVER-MAJOR)</1> <1>timers</1>: refactor error handling (Anatoli Papirovski) <2>#18486</2>

Spanish:

[<0>9b8e1c2e4f</0>] - <1>(SEMVER-MAJOR)</1> <1>timers</1>: refactorizar el manejo de errores (Anatoli Papirovski) <2>#18486</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: 1171.
• The total amount of words translated in this project (as a Da-vinci/Utopian translator) is: 17647.

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.

Proof of Authorship

This translation was made November 1st, 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].