[Translation][Spanish] Node.js, from English (1218 words) [N'20]

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 20th 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, which is the part of the document I worked in this occasion.

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

The first one is "string". Perhaps the mostly used element of programming, a string is an object class consisting in a character sequence that is written or read by a software. In the case of Node.js, strings are the messages passed between the different components of the program and between user and machine. Their versatility has no competitor in Java programming, since they are the input and output of basically all functionality related to it.

GIF source

The second term we need to define is "header". Do not confuse "headers" with "headings". While headings are the titles of common texts, in the context of programming, specifically HTTP related, headers are coding messages that are passed upon a network connection. They allow clients and servers to pass additional information in such connections, with requests and responses. There are several types of headers, according to their context, handling by proxies and function.

By context, they can be classified as:

• General headers
• Request headers
• Response headers
• Entity headers

By the way they're handled by proxies, they can be:

• End-to-end headers, when their data is transmitted directly to its final recipient.
• Hop-by-bop, when their data is single-used and must not be retransmitted.

Although there are a few others with very specific functionality, according to their use, headers can be:

• Authentication
• Caching
• Client hints
• Conditionals
• Connection management
• Content negotiation
• Controls
• Cookies
• Do Not Track
• Downloads
• Message body information
• Proxies
• Redirects
• Request context
• Response context
• Range requests
• Security
• Server-sent events
• Transfer coding
• WebSockets

Finally, as simple as it can appear, we need to clarify what is to "throw" in the context of Java programming. To throw is just the action of a program of reporting an exception or any common error occurred during the execution of its code.

-Really? That simple?
-Yes! But you didn’t know that!

(Maybe you did.)

Being so, a very defective program would look like this (where Buzz is the machine and the discs are errors... And their hits cannot be avoided).

THROW! THROW! THROW! THROW!

GIF source

Having explained all that, we can address the quoted entry. With the introduction of that update, objects that are not strings cannot be passed now as the content of a header in a HTTP test, as it was allowed before. Any intent of doing so will result in an error, as HTTP won’t be able to process them. With this commit, the programmers sought for a more strict regulation and prevision of the expected results of the tests being run for the HTTP component of Node.

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

• https://docs.oracle.com/javase/tutorial/java/data/strings.html
• https://www.geeksforgeeks.org/string-class-in-java/
• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers
• https://www.techopedia.com/definition/27178/http-header

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>7c73cd4c70</0>] - <1>net</1>: emit error on invalid address family (cjihrig) <2>#19415</2>

Spanish:

[<0>7c73cd4c70</0>] - <1>net</1>: emitir error ante familia de direcciones inválida (cjihrig) <2>#19415</2>

• Work example #02:

English:

[<0>de848ac1e0</0>] - <1>repl</1>: refactor tests to not rely on timing (Bradley Farias) <2>#17828</2>

Spanish:

[<0>de848ac1e0</0>] - <1>repl</1>: refactorizar las pruebas para que no dependan del tiempo (Bradley Farias) <2>#17828</2>

• Work example #03:

English:

[<0>1396996b02</0>] - <1>src</1>: use v8:: namepace consistently in node_file (Daniel Bevenius) <2>#20059</2>

Spanish:

[<0>1396996b02</0>] - <1>src</1>: usar de forma consistente el espacio de nombre v8:: en node_file (Daniel Bevenius) <2>#20059</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: 1218.
• The total amount of words translated in this project (as a Da-vinci/Utopian translator) is: 21564.

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.

Proof of Authorship

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