[Translation][Spanish] Node.js, from English (1327 words) [N'18]

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 18th contribution to Node.js as a translator. For this collaboration, I continued my previous work on CHANGELOG_V10.md file. This document contains an ordered list of the commit logs of all accepted pull-requests related to Node's Version 10.

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 one of the logs I translated to illustrate the dynamics of the changelog. This one belongs to the Semver-patch sub-section of the Commits.

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

The first one is "doc". Doc. refers to the section of Node that this commit is aimed at. It stands for documentation. As I explained in one of my previous reports, every single one of Node's components is registered in a vast organized compendium of documents. Each one of those describes their features and provides instructions on how to use them properly.

Image source

The other term we need to define is "linkification". It is quite simple! It refers to the process through which a piece of unformatted text is bound to an URL where to conduct the users who click on it. To the date, this is a feature contained in virtually all digital writing platforms: from text formatting applications, to e-mail services, cellphone texting, social media interfaces and (of course) web browsers! Linkification makes our lives easier:

Remember the URL of that article someone sent you the other day via WhatsApp? No. You don't... And neither would I. But that didn't stop you from opening it, since all you had to do was to click on it. Yes... You could have just copy-pasted it in the browser... But you know you're too lazy for that. So, say it with me: "Thanks, linkification!"

GIF source

Knowing these concepts, the comprehension of the quoted entry becomes possible. Node's platform had an error that was resulting in a failed linkification of particular contents of the documentation. To add more chaos to the situation, these failed processes showed themselves as successful (LIARS!). This commit represents the fixing of that bug in a way that it was assured it shouldn't have occurred ever again.

SPOILER ALERT: It happened again and got re-fixed.

You can check some references here –in addition to the Github repository of Node, which contains its documentation– for more information about the previously addressed concepts:

• http://sce2.umkc.edu/BIT/burrise/pl/appendix/Software_Documentation_Templates/
• https://en.wiktionary.org/wiki/linkification

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>51c2c51029</0>] - <1>doc</1>: explain edge case when assigning port to url (nodeav) <2>#19645</2>

Spanish:

[<0>51c2c51029</0>] - <1>doc</1>: explicar caso extremo al asignar un puerto a un url (nodeav) <2>#19645</2>

• Work example #02:

English:

[<0>a8533cf543</0>] - <1>doc</1>: add quotes for event names + fix similar nits (Vse Mozhet Byt) <2>#19915</2>

Spanish:

[<0>a8533cf543</0>] - <1>doc</1>: añadir citas para los nombres de eventos + corregir nits similares (Vse Mozhet Byt) <2>#19915</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: 1327.
• The total amount of words translated in this project (as a Da-vinci/Utopian translator) is: 18974.

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.

Proof of Authorship

This translation was made between 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].