[Translation][Spanish] Node.js (1208 words) (Part 66)

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 66# contribution to Node.js. As I have been doing for the last several contributions, the content I translated consists in instructions for changes that were originated posted in the GitHub platform, and eventually applied to Node.js with the goal of improving the project’s code.

These instructions were written by developers and for developers, which is why it is absolutely normal to see technical terms being used from time to time or to see some abbreviations. This means that sometimes, especially the first time the translator encounters an unknown term, it is necessary to take the time to do a little research so the translation can be as accurate as possible.

However, the majority of the instructions use simple terms, these are written with imperative verbs and in a very straightforward way. A few paragraphs above, I mentioned that these instructions are originally posted on GitHub, these postings are also included in the translated content. This information is included in a very practical way, the first element we see when translating the strings with instructions is the link to the GitHub commit where said instruction was posted. Sometimes there is also a brief explanation about the issue in question.

At the end of the string, we see the second link, this time it is the pull request link from GitHub that confirms the instruction was applied to the software. Adding this information can be of big help when trying to understand more about the reason behind these changes.

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

English

adjust function argument alignment

Spanish

ajustar alineamiento de argumento de función

This change was proposed because a new lint rule was about to be applied, and in order to avoid any issues, the best choice was to make the necessary adjustments before the rule was enforced. This instruction was applied, and everything went smoothly with the new rule.

^Source

---

English

add process.cpuUsage() - implementation, doc, tests

Spanish

añadir implementación, documentación, y pruebas de process.cpuUsage()

There was some information that needed to be updated, specifically information regarding “process.cpuUsage() method that returns the user and system CPU time usage of the current process” ^Source. Therefore, given the fact a developer realized the need to add this new information, he proposed this instruction.

---

English

fix v6 changelog

Spanish

corregir registro de cambios de v6

Every change that is applied to Node.js is added to the corresponding changelog. In this case, a developer noticed that part of the information for the changelog of Node.js v6 was missing. The developer wrote that “quite a few of the commits were missing from the original changelog generated for v6 relative to v5.11.0.” ^Source

This information is very important, because when doing translations like the one I did a few days ago, the changelog needs to have the correct data, otherwise, all the people checking the changelogs and the translations won’t be able to know every change that was applied in the previous version.

^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 66: 1208 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