[Translation][Spanish] Node.js (1109 words) (Part 32)

Source

Repository

https://github.com/nodejs/i18n

Project Details

Node.js is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code outside of a browser... Node.js allows the creation of Web servers and networking tools using JavaScript and a collection of "modules" that handle various core functionality... Node.js represents a "JavaScript everywhere" paradigm, unifying web application development around a single programming language, rather than different languages for server side and client side scripts. | Source

In simple words, this project brings value to the open source community because it facilitates the creation of all sort of applications using JavaScript, and provides a lot of help and versatility to developers, so much so that well-known companies like Netflix, Paypal, and Uber (among many others) use Node for their online services.

Since Node.js is very easy to learn and it provides a lot of benefits for developers, there is a huge community of people involved with it, which is one of the reasons why this project is available to be translated into several languages (in crowdin, one of the best translation platforms in the web, this project is available to be translated into 33 different languages, Spanish being the one corresponding to this contribution), the ultimate goal in translating Node.js is to make it easier for developers from any country to start learning about this project in their own native language.

If you want to know more about Node.js feel free to visit its website.

Contribution Specifications

• Translation Overview

This is my #32 contribution to Node.js, the project remains 29% completed just like in the previous contribution, and the folder I am working on, CHANGELOG_V6.md, is 59% completed.

This folder is basically a registry for all of the changes that were applied to Node.js V6, it is divided into several versions, for example 6.8.0 , 6.8.1… and each version is then divided into several sections, due to the fact that in this contribution I translated several versions that were very short, I can show how each of them is structured with just a single image:

Generally there is an introduction with general info about the particular version before the “Notable Changes” section, however in this case, the version was very short and all of its strings can be displayed with just one screenshot, we can see the commits section always have the same structure: the link to the GitHub issue – the area it is related to – the instructions for the change – the name of the person who proposed this change and finally the link to the pull-request in GitHub.

In the majority of the versions, the commits section is always the larger one, in fact, I recently worked with a version that had close to 100 strings in its commits section, so seeing a version with just 3 commits is something I wasn’t expecting.

On the other hand, when translating this type of strings it is very common to find technical terms and abbreviations, so sometimes the best thing to do is to take the time and do a little research about the meaning of some of those terms with the goal of doing the best possible translation. If by any chance any translator finds a technical term that he doesn’t know, then the best is to follow this advice from Sherlock Holmes himself!

Gif Source

Below I added a few examples of the translated strings:

English

generate UUID for debug targets

Spanish

generar UUID para objetivos de depuración

---

English

Vulnerability originally reported by Jann Horn.

Spanish

Vulnerabilidad originalmente reportada por Jann Horn.

---

English

All Node.js users should consult the security release summary at https://nodejs.org/en/blog/vulnerability/october-2016-security-releases/ for details on patched vulnerabilities.

Spanish

Todos los usuarios de Node.js deberían consultar el resumen de la actualización de seguridad en https://nodejs.org/en/blog/vulnerability/october-2016-security-releases/ para más detalles sobre vulnerabilidades parcheadas.

---

When working on this contribution I was able to learn the following concepts:

Watchdog: sometimes our software or hardware can malfunction for several reasons, a watchdog is an element with only one responsibility: to stay vigilant and detect if there is any malfunction in the system, and if there is one, then it triggers the necessary procedure to fix whatever problem there might be, in this sense, a watchdog should always remain vigilant, as Obama says in the following gif:

Gif Source

Text source 1

Text source 2

Text source 3

Continuous Integration (CI): as the name implies, CI consists in being constantly analyzing the code in order to identify potential bugs as quickly as possible, and start figuring out potential solutions. The goal is basically to fine-tune the software that is being used.

Text Source 1

In the previous contributions, I included the definition of these terms: deprecation, I/O - input/output, callback, asynchrony, POSIX, parsing, path, wildcard, wrapper function, stack trace, floating point value, error-first callbacks, transpilation tool, root certificate, little-endian, DNS rebinding, same-origin-policy, keep-alive behavior, stringification, arrow function, salt (cryptography), semver, lint, fixtures modules, newline, backporting, shell command, ES6 Classes , code refactoring, segfault, tarball, benchmark, type-check, deflate, char, aix, spawn, rehash, noop, rebasing, continuous integration, linkify, segfaults, IPC, libuv, toolchain, punycode, symlink, base64, interprocess communication (IPC), application binary interface (ABI), read–Eval–Print Loop (REPL), advanced Interactive eXecutive (AIX), GYP, Opaque binary blob (obb), symbolic link, destructuring, dotfiles, transport layer security (tls), and realpath function.

---

• Languages

Source language: English

Translated language: Spanish

I have made several contributions in the past, and I published a series of articles in both languages. I am also part of the Utopian + DaVinci Spanish team.

• Word Count

Part 32: 1109 words

Total: 35367 words

Proof of Authorship

My activity on Crowdin