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.
- Translation Overview
This is my #41 contribution to Node.js, the project is 36% completed, which is the same % from a few days ago when I posted my previous contribution, but I am sure we will be increasing the % very soon.
I am translating the folder named as CHANGELOG_V6.md, it is 84% completed, which means that on this contribution I translated an additional 2% of its strings. This particular folder is quite extensive because it has 42498 words in total, and so far I have translated 36101 of them. There are about 6500 words that still need translation.
The reason why this folder has so many words, is due to the fact that it serves as a registry for all of the changes that were applied to Node.js V6. This is a very normal dynamic because when developing any software, there will always be new innovations to add, and bugs to fix, which is why there are always people doing tests and figuring out ways to improve how a particular element works.
In the case of Node.js, the content regarding its changelog always follow a very strict structure, the entire folder is divided into several version, because there is not just one V6 version, there are many of them, in the following picture we can see the entire list of versions inside the general V6:
In this particular contribution, the majority of the translated strings were instructions explaining each and every change with the goal of improving the way Node.js was working. When I started to translate the strings belonging to version 6.2.1, I noticed there was a lot of information in the notable changes section:
There are some versions that don’t have notable changes, and the same happens with the introductory paragraphs, but this was probably the longest notable changes I have encountered when translating this folder.
Nevertheless, as I just mentioned, the majority of the translated strings were instructions, which means these strings belonged to the commits section, we can see a glimpse of this section in the following picture:
Below I added a few examples of the strings I translated while working on this contribution:
guard against undefined message handlers
protegerse de manejadores de mensajes indefinidos
add note about duration_ms in TAP reporter
añadir nota sobre duration_ms en reportero de TAP
fix test-net-* error code check for getaddrinfo(3)
reparar chequeo de código de error de test-net-* para getaddrinfo(3)
When working on this contribution I was able to learn the following concept:
Nit: as we all know, when developing software it is quite common to do little mistakes, but not all of those mistakes are serious, there are some imperfections that are small and even though they must be fixed, they aren’t necessarily a dangerous threat to the proper functioning of the software, these small mistakes are known as nits. Since nits are not a big deal, when someone does one of these little mistakes, saying whoops is a normal reaction:
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 and Coverity.
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 41: 1158 words
Total: 45960 words