[Translation][Spanish] Node.js (1079 words) (Part 28)

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 being the one corresponding to this contribution), the ultimate goal in 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 #28 contribution to Node.js, since this project is quite extensive, it is still 27% completed, just as in the previous contribution. The folder I have been translating, which is named CHANGELOG_V6.md, is currently 48% completed. This folder has all of the changes that were made to Node.js V6.

The considerable majority of the strings are short instructions that indicate a proposal for something that needs to be changed in Node.js V6. These changes can be related to code refactoring, improving documentation, fixing typos, updating tests, enabling and disabling all sort of internal Node.js elements, among many other changes.

These strings are then divided by sections each of them corresponding to a different version of Node.js. For example, in this contribution I finished version 6.10.0 and started with the version 6.9.5, which is a security release with a low impact for users according to Node.js crypto team.

All of the strings with proposals to apply changes are written in the most efficient possible way, with a lot of abbreviations and technical terms, and every time, there is the name of the person who proposed the change at the end of the string, and at the beginning, there is the link to the commit on github.

I added a few examples of the translated strings that we can see below:

English

Details on this determination can be found <0>on the Nodejs.org website</0>.

Spanish

Detalles sobre esta determinación pueden ser encontrados <0>en la página web Nodejs.org</0>.

---

English

This is a security release of the 'Boron' release line to upgrade OpenSSL to version 1.0.2k

Spanish

Esta es una actualización de seguridad de la línea de actualizaciones 'Boron' para actualizar OpenSSL a la versión 1.0.2k

---

English

do not refer to secureOptions as flags

Spanish

no referirse a secureOptions como banderas

---

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

• Symbolic link: every time a file has a reference to another file or directory, it has a symbolic link. When an operating system finds one of these, it will automatically follow the path to the file or directory that is being referenced by the symbolic link. The difference between a symbolic link and a shortcut is that the symbolic link will make it look as if the referenced file is in the same folder as the symbolic link, which is something that doesn’t happen with shortcuts.

Source 1

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, segfault, 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, and Opaque binary blob (obb)

---

• 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 28: 1079 words

Total: 30346 words

Proof of Authorship

My activity on Crowdin