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 67# contribution to Node.js. The content I translated for this contribution consisted mainly in instructions that explained some changes that were applied to this software, in order to fix bugs, issues and other mistakes that could have a negative impact in Node.js’s performance.
These instructions are originally written by developers and posted in the GitHub platform, which is why it is normal to see some strings with technical terms or abbreviations that are of common use for developers.
In order to make sure the translation of those technical terms is correct, it is necessary to take the time and research the actual meaning of the term, and then proceed with the translation.
The majority of the strings I translated follow a particular template, the first information we see is the link to the commit in GitHub where the instruction was originally posted. Then we will see the area related to the commit, such as “test”, “doc”, “stream”, “crypto”, among others. The next part of the string would be the instruction itself, which is always written using imperative verbs and in a very concise way. After that, we will see the name of the developer that wrote the instruction, and finally, we will see the link to the merged pull request in Github.
Below we can see a few examples of the instructions I translated.
English
update error message for JSON.parse
Spanish
actualizar mensaje de error para JSON.parse
As the software evolves and is improved, the same happens with the messages used to provide indications for the users and developers. On this occasion, a developer realized that the error message for JSON.parse needed to be updated, so he decided to share this instruction with the community. This change was eventually implemented and added to the official Node.js’s changelog.
English
add tests for console.assert
Spanish
añadir pruebas para console.assert
This change was proposed because there were “no tests where console.assert failed” Source. In order to fix this little issue, the developer posted the instruction to add the necessary tests, and everything got solved.
English
improve module loading performance
Spanish
mejorar rendimiento de carga de módulo
A developer figured out a way to improve the module loading performance. This improvement was possible thanks to the following measures:
- Try-finally/try-catch isolation
- Replacing regular expressions with manual parsing
- Avoiding unnecessary string and array creation
- Avoiding constant recompilation of anonymous functions and
function definitions within functions. Source
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 67: 1213 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:
