[Translation][Spanish] Node.js (1029 words) (Part 47)

Words
966
Reading
5 min
Listen
Play
8y

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 #47 contribution to Node.js, and the strings I translated were all from the commits section of version 6.0.0, which is the first version of the entire changelog folder.

In previous contributions, I translated all of the semver major changes, in my previous contribution I explained that these changes are those “when an important change is applied, that completely modifies the way an API works making it incompatible with older versions”. Source

But since that section was completely finished, I started to translate the information related to semver minor changes, let’s remember what are these changes all about:

… little changes that were applied are backward compatible, so the impact of this change is not as meaningful. Source

The instructions for both types of changes are always presented following a particular template, first we will see the corresponding link to the commit on GitHub, then the area belonging to change (tests, utilities, among others), the next piece of information in the string would be the instructions themselves, always written with imperative verbs and with the tendency to use abbreviations and technical terms, then we will find the name of the person who wrote that instruction, and finally, the link to the pull request on GitHub. Below I added some examples of these strings:

This template is used so the information is always presented with a simple but very useful and practical way, this can be of big help when it comes to managing all of the changelogs, and applying the necessary changes without losing control of the information.

Given the fact Node.js is a very common software, it is constantly being updated and improved, which is why there is always a big number of people proposing productive changes.

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

don’t write to input stream in editor mode

Spanish

no escribir a stream de input en modo editor

This was a required change, because it allowed to “instead of writing to the REPL’s input stream for the alignment spaces in .editor mode, let readline handle the spaces properly (echoing them using _ttyWrite and adding them to the current line buffer)”. Source


English

add note to parallelize make

Spanish

añadir nota para paralelizar proceso de compilación

This change was proposed because a particular user didn’t know this trick, and he “thought the build was stuck in an infinite loop”. Source


English

mention cc-ing nodejs/url team for reviews

Spanish

mencionar envío de duplicados a equipo de nodejs/url para análisis

This change was applied so the people that belonged to the nodejs/url github team could receive emails about the development of the WHATWG URL code.


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

JavaScript Object Notation (JSON): this is a very simple data format that makes it easier for people to read and understand the information, and computers can also easily check if there is any mistake in it, which makes it a very reliable and easy-to-use format.

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, 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, and rest parameters.


  • 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 47: 1029 words

Total: 52331 words

Proof of Authorship

My activity on Crowdin

[Translation][Spanish] Node.js (1029 words) (Part 47) | Ecency