[Translation][Spanish] Node.js (1215 words) (Part 61)
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 61# contribution to Node.js. The Spanish team has been progressing nicely in translating the entire Node.js project to Spanish. At this very moment, the project is 62% completed, which proves the hard work this team has been doing.
Regarding the content I translated for this contribution, it all belongs to the changelogs. A project as complex as Node.js needs to record every change it is applied with the goal of keeping all the information in proper order.
This is the reason why the information in the changelogs is organized using sections for each Node.js’s version. Each section usually has an introductory paragraph where it is informed the number of commits included, and the area to which they are related.
Sometimes there are also notable changes, which are a little bit different than regular commits because these changes are not only more important, but they are also written in a less concise way. All of the information about changes is originally posted by developers in GitHub, and then this information is uploaded to Crowdin to facilitate the translation activities.
The majority of the changes are regular commits with simple instructions, below we can see some examples:
English
skip cpu-intensive tests on slow hosts
Spanish
omitir pruebas que sean intensas para el cpu en hosts lentos
Some tests were overwhelming some of the weaker CPUs, so it was decided that these tests should be skipped in certain cases. Once this change was applied, a developer confirmed this was a good decision by saying:
it's looking good to me (only skipping the test on the Raspberry Pi 1 devices, running fine everywhere else). Source
English
modernize syntax, add strict checks
Spanish
modernizar sintaxis, añadir chequeos estrictos
As technology advances, it becomes necessary to constantly improve the syntax. In the case of Node.js this is almost an ongoing improvement because the software never stops getting updates of all sorts.
English
remove duplicate content from readline doc
Spanish
remover contenido duplicado de documento de readline
Give the popularity of this project, there are a lot of documents that are of great help when using Node.js. Sometimes there are typos or other types of mistakes in these documents, and they need to be fixed. In this case, the mistake was a duplicated sentence that was easily fixed.
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 61: 1215 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,
Thank you for submitting your contribution!
Node.js is a very interesting project that contains many code values and terms related to computer science. Its difficulty relies on the fact that we must pay a lot of attention to the code in order to deliver the most accurate translation possible.
You did a very good job with your presentation post, it explains the purpose of the text you translated in a clear and precise way. You also included useful concepts you learned while working on this contribution, as well as examples.
Since you have plenty of experience with Node.js it's no surprise that you delivered an accurate translation once again. Your wording and spelling are correct for the Spanish language, as well for the project.
Keep up the good work!
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, @marugy99! 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!