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 76# contribution to Node.js. The information I translated for this contribution belonged to Node.js’s changelogs, and the majority of the translated strings were commits originally posted in GitHub by the development community.
Given the fact Node.js is a very popular open source software with a lot of companies using it, there are always new changes and innovation that are constantly added to this software with the goal of making it a better tool with more features and with a more efficient performance.
In order to keep all of the information in order, the strings with instructions are always written following the same structure:
The first information we encounter when translating these strings, is the link to the original commit from GitHub. This is where the instruction was first posted and shared with the entire community.
Then we will see a word indicating the area related to the instruction, some common ones are “test”, “doc”, “n-api” among many others.
After this, we will see the instruction itself, which is always written using imperative verbs and in a very concise manner. It is not a surprise to sometimes see technical terms or abbreviated words.
Then we will see the name or username of the person who originally wrote this instruction.
And finally, we will see the GitHub link that will take us to the merged pull request in GitHub.
Below we can see a few examples of the instructions I translated.
English
improve Transform performance
Spanish
mejorar el rendimiento de Transform
The entire development community is always looking for ways to make improvements to Node.js, this time, a developer realized there was a particular element that wasn’t performing as it should, so he informed the community about this issue and indicated the need for a solution.
English
fix section title typo
Spanish
corregir el error tipográfico del título de la sección
Sometimes there are a few typos in the documentation, and when the developers double check the writings, they usually discover these little mistakes. Since the goal is to have perfect documentation, every typo should always be fixed as soon as it is discovered.
English
fix link in async_hooks.md
Spanish
corregir enlace en async_hooks.md
On this occasion, a developer realized there was a broken link in a particular document. This can happen when the links aren’t properly updated when they should. Just as with typos, these little issues are always fixed as soon as they are discovered.
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 76: 1208 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:
