[Translation][Spanish] Node.js (1023 words) (Part 46)

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 #46 contribution to Node.js, on this occasion, every string I translated belonged to the same commits section I started in my previous contribution, which means the content I translated was from the version 6.0.0.

I finished the Semver-major changes and started to translated the Semver-minor changes and the patches, in the following picture we can see how this commits section is divided into those 2 types of changes:

Semver is an abbreviation of semantic versioning, which is a method that allows developers to organize the different versions of their software based on the type of change that was applied. With Semver, there are 3 categories:

1. The first one and the most important is known as Semver-major, this happens when an important change is applied, that completely modifies the way an API works making it incompatible with older versions.

2. Then we have Semver-minor, which means the little changes that were applied are backward compatible, so the impact of this change is not as meaningful.

3. Finally, we have the simple patches and bug fixes that are also backward compatible.

In the image I included above, we can see the start of the section corresponding to Semver-minor changes and patches, in fact, the majority of the strings I translated were from this particular section, and the intrusctions for the changes were always very direct and simple to understand.

However, regarding if the changes are included in the Semver-major or in the Semver-minor section, they are always written following the same template, which is clearly a method to present this important information in a uniform way, as well as facilitating their analysis and interpretation.

Below I added a few examples of the strings I translated from while I was working on this contribution and I also added a little explanation about each change:

English

add a temporary fix for re-evaluation support

Spanish

añadir una solución temporal para el soporte de re-evaluación

This was a temporary fix that was reverted in V7, the reason why they applied this temporary fix was “to give users a grace period before actually breaking modules that re-evaluate fs sources from context where internal modules are not allowed.” Source

---

English

remove redundant parameter comments from fs

Spanish

remover comentarios de parámetro redundante de fs

Node.js is a software that is constantly being updated, this is why there were some old version parameter comments in fs.markdown and with the goal of avoiding confusion, a change was proposed to remove redundant comments.

---

English

prevent node from running on Windows Vista or earlier

Spanish

evitar que nodo se ejecute en Windows Vista o anteriores

This was done to avoid suffering from incompatibilities in old systems.

---

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

Rest parameters: what this type of parameter allows, is to represent and have access to several arguments as an array, so it becomes easier for a function to use the argument it needs, effectively increasing its own versatility. There is no specific limit regarding the maximum number of arguments.

Text source 1

Text source 2

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, and TPR records.

---

• 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 46: 1023 words

Total: 51302 words

Proof of Authorship

My activity on Crowdin