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 71# contribution to Node.js. My contribution is focused on the content inside Node.js’s changelogs, inside these folders we can find all the information about every single change that was applied to improve the performance and functionality of this software.
Each version of Node.js has its own changelog’s folder, and inside these folders, there are always several sections for each sub-version of the software. This way, the information can be presented in an orderly manner for anyone interested in learning about previous changes.
Besides the instructions for each change, each string also has relevant links to GitHub which is where the instructions for changes are originally shared. GitHub is a platform that facilitates the communication and collaboration with the global development community for open source projects.
For each change the following information is usually shared:
Below we can see a few examples of the instructions I translated.
English
remove no-longer-relevant comment
Spanish
remover comentario que ya no es relevante
A software that is always evolving such as Node.js, will have constant changes and improvements that can modify the code and should also modify or adapt the documentation according to the applied changes. In this case, a developer realized there was a comment that was outdated and contained information that was no longer usable due to recent changes in Node.js’s code. Therefore, he indicated that this comment should be removed and that is what happened eventually.
English
add parentheses to refreshTmpDir()
Spanish
añadir paréntesis a refreshTmpDir()
A developer explained that since common.refreshTmpDir() is a function, it should have the corresponding parentheses to make it clear. Give the fact this was a very simple instruction this was quickly applied and the issue was solved.
English
ensure collaborators validate commits
Spanish
asegurarse de que los colaboradores validen los commits
It is important that collaborators take the time to validate commits because this would certainly reduce the potential errors and mistakes that could happen when creating the commits. This change was proposed to inform the collaborators that they should review their commits before submitting them.
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 71: 1207 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:
