[Translation][Spanish] Node.js (1211 words) (Part 79)
Repository
https://github.com/nodejs/i18n
Project Details
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.
Contribution Specifications
- Translation Overview
This is my 79# contribution to Node.js. For this contribution continued to translate information from Node.js’s changelog. Inside these folders, we can find all the necessary information people might need that is related to changes that were previously applied to this software. For example, in each string containing an instruction, we will also see information about the area related to the change itself, about the person who proposed the particular change and the corresponding GitHub links where the instruction was originally posted.
This way, any individual who wishes to dig a little bit deeper and learn more about a particular change, can easily do it. In Github, there are usually short discussions for each change that is applied, so in order to clear any potential doubt about an individual change, we can visit the GitHub discussions and see what the developers were saying.
The reason for so many Node.js’s changelogs is because this software is incredibly popular and its open source nature makes it easy for any person with technical knowledge to understand how its internal elements work. This results in a community of developers willing to share their efforts in improving the software.
Below we can see a few examples of the instructions I translated.
English
update root certificates
Spanish
actualizar certificados root
This type of certificate is very important to handle important information in a very secure way. Updating them ensures the software is working with up-to-date information and not outdated or deprecated certificates that could harm the performance of the software.
English
remove unnecessary template class
Spanish
remover la clase de plantilla innecesaria
It is important to remove internal elements that aren’t useful for users or developers because this can increase the efficiency of the software. This time, a developer discovered a template class that wasn’t used “in the template specialization following it”, so the decision was to remove it.
English
add support for abi stable module API
Spanish
añadir soporte para la API del módulo estable de abi
Adding support for APIs is important to make sure Node.js works in an optimal way. This feature was added as a kind of experiment to see how things will go, which is a very wise thing to do because innovation should never be rejected.
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.
- Languages
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.
- Word Count
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 79: 1211 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:
Greetings, @dedicatedguy. Thanks for submitting your contribution!
Congratulations on this collaboration!
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Chat with us on Discord
Thank you for your review, @alejohannes! Keep up the good work!
Hi @dedicatedguy!
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server
Hey, @dedicatedguy!
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!