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 62# contribution to Node.js. The translation activities mainly consist in instructions that are meant to improve the way Node.js works. These instructions are written by developers who are active Node.js users and every time they realized there is a small bug, mistake or issue, they figure out the solution and share it using the GitHub platform.

Give the fact this software is open source, every developer has access to its code and can modify it as they see fit. All of these modifications are discussed in the aforementioned Github platform because this is the best way to work along with the global developer community that uses this software.

After a developer identifies an issue, it is informed and discussed, and eventually, a solution is reached. These solutions are then added to the Node.js changelogs with the goal of having a proper record regarding every modification applied to the software.

The information inside the changelog is the one I have been translating. These instructions come straight from Github which is why they always have the corresponding Github links embedded. The majority of the translated strings are simple instructions to change something within Node.js to fix an existent problem.

However, there are also other strings that instead of simple instructions they have introductory paragraphs, or information about notable changes.

Below I will add a few examples of the translated strings:

English

change ContextifyScript to Script in comment

Spanish

cambiar ContextifyScript a Script en comentario

A developer was checking a comment in vm.js when he realized there was a small mistake because instead of saying Script the written word was ContextifyScript, which in this case was not the more accurate term. Therefore, he proposed a simple instruction to fix this little mistake.

---

English

enable caching for jslint task

Spanish

habilitar almacenamiento en caché para la tarea de jslint

A developer realized that using cache memory would result in a faster time when running a certain process. Because of this, he proposed to enable this memory in order to improve the performance. This discussion can be found here.

---

^Source

English

modernize JS and tighten equality checking

Spanish

modernizar JS y endurecer chequeo de igualdad

Node.js is a software that is in constant improvement and there are always people figuring out ways to make it function in a better way. In this case, a person made a proposal to make sure the code is top notch so the software can keep its optimal performance.

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, rest parameters, javaScript Object Notation (JSON), N-API, primitives, and CVE.

---

• 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

The word count of this contribution is the number of words translated after subtracting words that aren’t changed, such as names, links, functions.

Part 62: 1209 words

The total numbers of words includes every word in the final translated strings, including those that aren’t actually translated, such as names, links, functions.

Total:

Proof of Authorship

My activity on Crowdin

---