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

in #utopian-io6 years ago

NodeJS.png
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 24th 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.5.0. The first one goes:

Screen Shot 2018-12-18 at 1.31.45 PM.png

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

The first one is "Base64". Base64 is a text encoding scheme where each digit stands for 6 bits of data. It is used to ensure that certain binary data that is passed through networks is interpreted as what it is and not mistaken for security protocols and special character keys settings. It's first implementation was in 1987, with the Privacy-enhanced Electronic Mail (PEM), as it was described in the RFC #989. This coding has plenty utilities for Node.js, which is why its crpytographic tools include support for it and are constantly updated.

The following is the Base64 encoding table, so you, programming geeks have an idea of how it goes:

base64table_thumb.jpg

Image source

The second one is "decoding". As it is defined by the Oxford dictionary, the act of decoding consists in the conversion of a coded message into intelligible language. In cryptography, this is one of the basics, and, in programs like Node, that constantly require to work with multiple codifications, it is indispensable that the components in charge of that action are kept tuned and up to date.

This is a funny, very simplified and full of good vibes decoding example:

secretmsg.gif

Gif source

Once that is clarified, we can understand that this commit seeks to upgrade the decoding mechanism of Node.js for the Base64 encoding, making it a 50% faster and, by that, improving the overall performance of the program.

The second log I'll refer is this:

Screen Shot 2018-12-20 at 11.43.39 PM.png

To understand this commit, we need to know what a digital fingerprint is. As a human fingerprint, a digital one is an unique mark that large data items have, has a much smaller size, and allows programmers to track and identify such item without having the necessity to parse the whole file looking for it.

download (3).jpeg

Image source

That being said, we can understand the addressed commit. It seeks to create a fingerprint for the collaborator cjihrig within the the Complexity Profile Graph (CPG) usage by Node.js.

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

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.

changelog.png
Image source

  • Work example #01:

English:

Introduce a new <0>process.release</0> object that contains a <0>name</0> property set to <0>'io.js'</0> and <0>sourceUrl</0>, <0>headersUrl</0> and <0>libUrl</0> (Windows only) properties containing URLs for the relevant resources; this is intended to be used by node-gyp (Rod Vagg) <1>#2154</1>.

Spanish:

Introducir un nuevo objeto <0>process.release</0> que contenga una propiedad <0>name</0> establecida a <0>'io.js'</0> y propiedades <0>sourceUrl</0>, <0>headersUrl</0> y <0>libUrl</0> (solo en Windows) que contengan las URLs de los recursos relevantes; esto está destinado a ser utilizado por node-gyp (Rod Vagg) <1>#2154</1>.

  • Work example #02:

English:

Removed <0>SetIndexedPropertiesToExternalArrayData</0> and related APIs, forcing a shift to <0>Buffer</0> to be reimplemented based on <0>Uint8Array</0>

Spanish:

Fueron removidas <0>SetIndexedPropertiesToExternalArrayData</0> y las APIs relacionadas, forzando a que se produjera un cambio y <0>Buffer</0> fuese reimplementado basándose en <0>Uint8Array</0>

  • Work example #03:

English:

Calling <0>dns.setServers()</0> while a DNS query is in progress can cause the process to crash on a failed assertion. #894

Spanish:

Llamar a <0>dns.setServers()</0> mientras una consulta de DNS está en progreso puede ocasionar que el proceso colapse ante una aserción fallida. #894

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

Previous Translations of the Project

Proof of Authorship

This translation was made between December 15th and 18th, 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].
Crowdin Profile.png

Sort:  

Hi @alejohannes,

Thank you for submitting a new contribution!

  • Node.js is a very interesting project that contains many code values and terms related to computer science. Its difficulty relies on the fact that we must pay a lot of attention to the code in order to deliver the most accurate translation possible.

  • You did a great job with your presentation post, it is well written and formatted. It also includes all the basic details, as well as your personal feedback. You shared clear and precise concepts you learned while working on this contribution in a very dynamic way.

  • Once again, you delivered an accurate translation. You used the correct vocabulary and you were careful with code values that should not be translated in order to make sure the text keeps its true meaning.

Keep up the good work!

Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.

To view those questions and the relevant answers related to your post, click here.


Chat with us on Discord

Thank you for your review, @marugy99! Keep up the good work!

Hi @alejohannes!

Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server

Hey, @alejohannes!

Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!

Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).

Want to chat? Join us on Discord https://discord.gg/h52nFrV.

Vote for Utopian Witness!

Coin Marketplace

STEEM 0.19
TRX 0.14
JST 0.030
BTC 60115.50
ETH 3192.77
USDT 1.00
SBD 2.45