[Translation][Spanish] Node.js (1209 words) (Part 56)

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

This is my 56# contribution to Node.js, and I continued to translate strings mainly consisting of instructions that were originally posted on GitHub, and later uploaded to Crowdin to facilitate the translation of this important content.

It is very interesting to see how some of the commits from GitHub are sort of integrated into Crowdin in a very orderly way. When it comes to the changelogs, they are all divided by version and then by the sub-version inside each major version.

The information in each these sub-versions is then usually divided into several segments, mainly consisting in a kind of introduction giving information about the total number of commits belonging to this version, there are also a little paragraph indicating the notable changes whose length can vary a lot, and the final segment of each sub-version is the commits section, which as mentioned before, are instructions originally from GitHub about changes that need to be applied in order to improve any issue that might be affecting Node.js.

These commits are almost always written in a very concise way, using imperative verbs and it is also very common to see the use of abbreviations and some technical terms from time to time, but this is totally understandable because these commits are written by developers and for developers.

Given the fact these commits are created by individual developers, they always have the name of the person who proposed the change, as well as the are that is affected by this change, for example some common ones are path, tools and test.

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

English

add supported platforms list for v6.x

Spanish

añadir lista de plataformas soportadas para v6.x

It is very important to have this information updated because by directly informing the developers which platforms are supported it makes the work easier for them. Besides, it is always good to have all the information properly updated, especially with software as common as Node.js.

I imagine the list of supported platforms could be as long as this one!

^Source

---

English

use correct tls certificate property name

Spanish

usar nombre de propiedad de certificado tls correcto

The problem in this case was caused by an error in a document where it referred to a mistaken property. Specifically, the doc referred to a ‘issuer’ property, and the correct one was a ‘issuerCertificate’ property. ^Source

---

English

fix misleading ASCII comments

Spanish

corregir comentarios engañosos de ASCII

This change was proposed because there was a document with errors in some references to ASCII regarding default encoding examples. There was even a little discussion in GitHub about this issue, which can be found here.

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 56: 1209 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: 68442 words

Proof of Authorship

My activity on Crowdin