[Translation][Spanish] Node.js (1207 words) (Part 82)

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.

Source

Contribution Specifications

• Translation Overview

This is my 82# contribution to Node.js. The project is currently 75% translated for the Spanish language. These translation activities are handled through the Crowdin platform and the Spanish team is the one that has contributed the most for the localization of this project.

The content I translated for this contribution belongs to the changelogs folders. Inside these folders, we can find all of the information related to each and every single change that has been applied to previous Node.js versions. Given the fact this software has a very active development community, it is always being updated and improved.

Node.js is also an open-source project, which allows developers from all over the world to gain access to its source code and propose improvements and all sorts of solutions for each issue that might arise, this is why there is always a high number of people giving their best effort towards the development of Node.js.

Below we can see a few examples of the instructions I translated.

English

remove unused openssl files

Spanish

remover archivos de openssl no usados

A developer discovered several openssl files that didn’t have any use whatsoever, so with the goal of keeping removing every element that doesn’t add value to Node.js, he informed the need to remove these files.

---

English

fix json doc generation

Spanish

corregir la generación de documentos de json

There was a function in ‘tools/doc/json.js’ that wasn’t working properly. Luckily, a developer discovered this issue and informed the community about it. In due time, the problem was solved and the json doc generation started to work perfectly again.

---

English

fixing API refs to use safe internal refs

Spanish

corregir las referencias de API para que usen referencias de seguridad internas

This was a technical change proposed by one of the developers working with Node.js. He concluded that the use of internal refs was safer than otherwise. Applying this change would make Node.js a more robust software, so eventually, the change was applied.

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 82: 1207 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:

Proof of Authorship

My activity on Crowdin