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 #42 contribution to Node.js, and right after finishing it I could see that this project was 37% translated for the Spanish language. In my previous contribution we were at 36%, so that means in the last 2 days the Spanish team has added an additional 1% to the overall project.

The majority of my translations for this project have been to the folder known as CHANGELOG_V6.md, in this very moment the folder is 87% completed, and it has about 5000 words that still need to be translated.

Node.js is a project that evolves as time goes on, it has several versions where all sorts of updates are registered, and given the fact it is such a well-known software, it is constantly going through new optimizations and changes to improve its performance.

The folder I mentioned before (the one I am currently translating) has all of the information about the changes that were applied to Node.js V6, however, given the fact there is a lot of information, this type of folder always follows the same structure.

First of all, V6 is not just one version, in the following picture I took from the CHANGELOG_V6.md folder, we can see all of the different versions inside the general V6:

The way this folder is structured is actually quite simple and also very useful to have a proper distribution of the information.

As people might think after seeing the previous picture, the folder is divided into all of the different versions inside V6, this picture shows what I mean:

In the picture we can see the beginning of version 6.2.1, every version always begin in the same way.

Inside each version there is a common structure that is always followed, in that same image we can see the beginning of the first section of that particular version, in this case, it is the notable changes section, its name is very self-explanatory so I am sure everyone will know what type of information people can find in those strings.

But not every version is always the same, there are other versions that begin with some introductory paragraphs, and others don’t have any notable changes, so it varies from version to version.

The regular changes belong to the commit section:

And even in the strings inside the commits section, there is also a common structure that is followed most of the time. Below I will mention each part of this structure:

1. commit link from GitHub
2. area related to the change
3. instructions for the change, sometimes using abbreviations and technical terms to make it as concise as possible.
4. name of the person who proposed the change
5. link to the pull request on GitHub

That is the basic structure for the majority of the strings from the commits section, and since this section is always the most extensive one, the majority of the strings belonging to this folder are also structured like that.

These are a few examples of the strings I translated while working on this contribution:

English

add --preserve-symlinks command line flag

Spanish

añadir bandera de línea de comando de --preserve-symlinks

---

English

added tests for https-agent-getname

Spanish

se añadieron pruebas para https-agent-getname

---

English

don't install node_internals.h

Spanish

no instalar node_internals.h

---

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

Backtick: maybe the most simple way to understand the implication of using backticks when coding, would be to see it as a command inside a command. A backtick allows a string to be executed and the result of said execution is later used by the general command.

Text source

Hashes: these are the results developers get after applying a hash function to a particular value. The goal is to simplify values into ones that are shorter and simpler. One of the benefits of this is that it makes it easier to search for information in a database, because when using hashes, everything can be done faster and in a more efficient way.

Image source

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

---

• 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 42: 1127 words

Total: 47087 words

Proof of Authorship

My activity on Crowdin