[Translation][Spanish] Node.js (1217 words) (Part 54)

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 is the one corresponding to this contribution), the ultimate goal of 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

After a short break in my translation activities, I am glad to be back with a new contribution.

^Source

This is my 54# contribution to Node.js, and I am mostly translating commits, which means the majority of the strings I encounter are short and simple instructions about changes that must be applied to Node.js with the goal of improving the way this software is working.

Since I am working with very short strings, it is absolutely normal to find myself translating some technical terms and some abbreviations, but given the fact I started to work on this project a few months in the past, I am already accustomed to the style used in these strings, this makes it easier to do the translation job.

A very important aspect of this type of string, is that they always have a link to a commit on Github, where we can find more information about the problem that is being solved and sometimes there are even some explanations from the developer that proposed this particular change. Besides the aforementioned link, each string also has a link to the merged pull request is something that only happens after the proposed changes are accepted and integrated into the software.

Some examples of the instructions I translated can be seen below:

English

use mustNotCall() in test-fs-watch

Spanish

usar mustNotCall() en test-fs-watch

This instruction was proposed because there were some tests that were wrongly calling the function “watch()”. This is why a change was proposed to avoid that function from being called.

---

English

simplify test skipping

Spanish

simplificar omisión de pruebas

Skipping tests should be something fairly simple to do, but one developer considered that this process was kind of messy, which is why he made the following request “Don't make needless things before skip”. ^Source

Eventually, this change was accepted and the string was added in the crowdin platform to be translated.

---

English

add missing zlib link to stream API docs

Spanish

añadir enlace de zlib faltante a documentos de la API de stream

This change was proposed because a developer noticed that a link was wrongly deleted by mistake in a previous pull request, therefore, this developer created a new commit with the instructions to put this link back where it belongs in the corresponding document.

I imagine this developer had the following reaction after seeing that link being removed by mistake:

^Source

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, 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), realpath function, watchdog, continuous integration, smoke test, hotfix, data execution prevention, (DEP), try/catch blocks, off-by-one error, carriage return, ESLint, hard code, hook, Resource Acquisition Is Initialization or RAII, Coverity, nit, backtick, hashes, big endian, nop, redux, shorthand, TPR records, rest parameters, javaScript Object Notation (JSON), N-API, primitives, and CVE.

---

• 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

The word count of this contribution is the number of words translated after subtracting words that aren’t changed, such as names, links, functions.

Part 53: 1217 words

The total numbers of words includes every word in the final translated strings, including those that aren’t actually translated, such as names, links, functions.

Total: 63256 words

Proof of Authorship

My activity on Crowdin