https://github.com/nodejs/i18n
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.
This is my 70# contribution to Node.js. The content I translated for this contribution consisted mostly in instructions about changes that were previously applied to this software with the goal of improving its performance. Node.js is extremely popular and thanks to its versatility and features it has users from all over the world. This is why there are always a lot of people interested in solving any issue that could be affecting this software.
Another reason that explains why the development of Node.js is an ongoing and never-ending process is its open source nature. This makes it possible for any person to make their own voluntary contributions and participate in the general improvement of the software. This is especially useful for people with technical skills such as developers because this allows them to modify and experiment with the code.
The majority of the strings I translated were simple instructions that always follow the same writing style and structure. They usually start with an imperative verb and the text is always written in a very concise way. Given the fact all of these instructions were originally posted on GitHub, we will always find the link to the original commit posted on that platform, and the link to the merged pull request. Each instruction always has the name or username of the person who wrote it and the area related to the instruction itself.
Below we can see a few examples of the instructions I translated.
English
use default assertion message
Spanish
usar el mensaje de aserción predeterminado
The custom message that was being used didn’t show the value that was causing the test to fail. It only showed the expected value, but not the actual value that was used. Therefore, this developer proposed to switch back to the default message that does provide the complete information.
English
add a test description
Spanish
añadir una descripción de la prueba
A test didn’t have a proper description, and it is always useful for other developers to have a description for each test. Since this information was needed, a change was proposed to fix this little issue, and eventually, a proper description was added to the test.
English
test search module
Spanish
probar módulo de búsqueda
Each module should always be tested in order to make sure there aren’t any bugs or errors that could cause problems down the road. Since the search module had not been properly tested, a developer figure out this was something that had to be done, therefore, he proposed that instruction and fortunately everything went all right with the test.
I imagine this was the developer's reaction after knowing the test went all right:
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.
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.
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 70: 1205 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:
