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 81# contribution to Node.js and the content I translated was mainly short instructions regarding changes from previous versions of this software. Every single change that was applied to make Node.js a better software is registered in the corresponding changelogs.
These instructions are originally posted by members of the development community in GitHub, and later on, the information is reuploaded to the Crowdin platform to facilitate the translation activities. Given the fact this software is highly popular, it is constantly being updated and new changes are always being added, therefore, the information inside the changelogs is quite extensive.
These instructions are always written in a very concise form, always using imperative verbs and it is quite common to see abbreviated words or technical terms. The reason for this is that these instructions are written by developers and for developers, they aren’t meant to be read by non-technical users.
Below we can see a few examples of the instructions I translated.
English
improve querystring.parse assertion messages
Spanish
mejorar los mensajes de aserción de querystring.parse
It is always important to have all of the information presented in the best possible way. A developer thought there were some assertion messages to ought to be improved, so he shared this instruction with the community and eventually the messages were indeed improved.
English
fix gcc 7 build errors
Spanish
corregir errores de compilación de gcc 7
Sometimes when creating builds there could be errors that disturb the developer’s experience and can also affect the performance of the software. A developer discovered one of these errors and indicated the need for a proper fix.
English
remove unused declaration
Spanish
remover declaración no utilizada
There is no need to keep information that is no used nor needed. A developer discovered a declaration that didn’t serve any purpose, so he informed the community that the best decision would be to simply remove this declaration.
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 81: 1201 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:
