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 #35 contribution to Node.js, the project currently finds itself 31% completed, and the folder I have been translating, CHANGELOG_V6.md, is 67% completed. After working on this particular folder for several contributions, it is natural to get used to it, especially with how it is structured and with the proper way to translate every type of string we can find in here.

Due to the fact this folder has all of the information regarding the changes for Node.js V6, it is quite extensive, and when checking its strings, we can see it is properly ordered, always following the same structure.

The entire folder is basically divided into several versions, each of them containing their corresponding changes, and each of these versions is also divided into several sections. The structure of a version is something like this: tittle – introductory paragraphs – notable changes – commits.

Each section is always written following certain guidelines, however, not every version has all of those sections, something there aren’t any notable changes, and other times there aren’t any introductory paragraphs, but there are always commits because this is where we can find the changes for the particular version, therefore, the commits section is the most important and extensive one of this entire folder.

These commits are written following a certain format. In them we will always find the link to the commit on GitHub, the area that is related to the change in question, the instructions for the change (always with imperative verbs, and sometimes with technical terms and abbreviations), the name of the person who wrote these instructions, and finally the link to the related pull-request on GitHub.

The instructions to apply changes can be related to all sort of things, sometimes these are instructions to refactor tests or increasing their coverage, making changes to documents, adding information related to upgrades on modules, and other similar instructions related to internal elements and the internal functioning of this software.

Below I added some examples of these instructions:

English

simplify buffer management

Spanish

simplificar manejo de buffer

---

English

fix connection upgrade checks

Spanish

reparar chequeos de actualización de conexión

---

English

improve fs.truncate functions' documentation

Spanish

mejorar documentación de funciones de fs.truncate

---

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

Off-by-one error: this is a type of error that happens when the developer makes a mistake when writing the code, and gets confused when numbering certain elements depending if he started to count on 0 or on 1, even though this is just a basic example, this error is always related to miscounting.

It can happen when determining the length of an array, or the number of loops for a particular procedure. Identifying this type of error can be a bit challenging sometimes, so it is common to have reactions like this one coming from developers when they made an off-by-one error:

Gif Source

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, 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, Opaque binary blob (obb), symbolic link, destructuring, dotfiles, transport layer security (tls), realpath function, watchdog, continuous integration, smoke test, hotfix, data execution prevention (DEP), and try/catch blocks.

---

• 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 35: 1152 words

Total: 38935 words

Proof of Authorship

My activity on Crowdin