[Translation][Spanish] Node.js (1031 words) (Part 45)

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 #45 contribution to Node.js, and every single one of the strings I translated belonged to version 6.0.0. Being the first one, it has the biggest notable changes section in the entire folder, with changes that are related to the console, buffer, dependencies, DNS, modules, timers, among many others.

Once I finished with the translation of the notable changes section, I started with the commits section, in the following picture we can see a glimpse of both sections:

As we can see, at the beginning of the commits section, we are told that those are the semver-major changes since version 5.0.0, which explains why there are so many of them.

The type of instruction I found in this folder were always very simple and straight to the point, some changes were about improving the class of a certificate, improving certain documentation, applying checks to internal elements, among many other examples.

With the goal of presenting the information related to the changes in an uniform way, these strings always follow the same structure, which contains the following information in the same order: the link to the commit on GitHub, the area related to the string, the instruction written in the most concise possible way, the name of the person who proposed this change, and finally the link to the merged pull-request on GitHub.

To understand what I mean with “area related to the string”, it is easier to explain it with the help of a picture:

We can see the particular area of the first string is “doc”, the second one is related to “doc, tls”, the third one is related to “domains”, and so on. In this example, each string includes the term “SEMVER-MAJOR” because as explained before, these strings are every Semver-major change since version 5.0.0.

Below I added a few examples of the strings I translated from the commit sections while I was working on this contribution:

English

prioritize current dir for local lookups

Spanish

priorizar directorio actual para búsquedas locales

This particular change was proposed because there was a bug that caused a third party module to be referred over to another module that had the same name. This change fixed that little bug.

---

English

emit key info unconditionally

Spanish

emitir información clave incondicionalmente

This was proposed because there were 'keypress' events that included the sequence and key info for named keys, but only the sequence for unnamed keys. After applying this change the key info is going to be included in both cases.

---

English

fix the error report on fs.link(Sync)

Spanish

corregir el reporte de error en fs.link(Sync)

---

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

PTR record: usually, when people are using the internet and want to visit a website, the normal procedure is to write down the name of the website and go directly to it, each website has an IP address attached to it and the reason why we use the website’s names instead of IP addresses is because it is easier for us to do so, our computers are the ones that manage all of the IP information on their own, so basically, we input a website’s name, and our computers translate this information into an IP address.

What a PTR record allows is the exact opposite, it makes it possible to see which website’s name is linked to a particular IP address, this is mostly used to prevent spams in people’s emails.

Text source 1

Text source 2

Text source 3

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, and shorthand.

---

• 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 45: 1031 words

Total: 50279 words

Proof of Authorship

My activity on Crowdin