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 #34 contribution to Node.js, after finishing it I checked the progress of the Spanish team, and right now this project is 31% completed, this is again an increase in 1%, just as the one I mentioned in my previous contribution.
The folder I have been translating is CHANGELOG_V6.md, it is 65% completed, which means in this contribution I translated 3% of its strings. Inside this folder there is all the information related to every single change that was applied to Node.js V6. The folder follows a certain structure because the strings are divided into different versions, and each of these versions is then divided into several sections.
We can see what I mean when I say different versions by checking the following pictures where I share the titles of the version 6.14.0 and 6.13.1:
The complete list of versions can be seen in this image:
Each version contains its corresponding information properly structured, some versions have introductory paragraphs where general information about the strings is mentioned, while others don’t have much information because the number of changes is very low. However, the majority of the strings are always related to the instructions about the changes that must be applied in order to improve both Node.js performance and its documentation.
These instructions are always written in a very concise way, with imperative verbs, and with an efficient use of words, which is why it is very common to find technical terms and abbreviations in this type of string, this means I must take the time to research these words so the translation can be as accurate as possible.
Below I added some examples of these instructions:
English
improve coverage of the util module
Spanish
mejorar cobertura del módulo de utilidades
English
upgrade openssl sources to 1.0.2j
Spanish
actualizar fuentes de openssl a 1.0.2j
English
expand test coverage for url.js
Spanish
expandir cobertura de prueba para url.js
When working on this contribution I was able to learn the following concept:
Try/catch blocks: this is used when a code with one or more bugs is running. The "try" block contains information about the exceptions that can happen when executing the program, and the "catch" block is the one responsible for handling these exceptions so they don’t escalate. There is usually more than one "catch" block linked to the "try" block, and this will depend on the number of known exceptions.
Basically, a "catch" block, like its name implies, must catch exceptions, like this guy here is catching the ball:
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 and data execution prevention (DEP).
- 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 34: 1206 words
Total: 37783 words