[Translation][Spanish] Node.js (1211 words) (Part 59)
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 59# contribution to Node.js, the strings I translated are those belonging to Node.js’s changelog, which means they provide all of the necessary information about every modification recommended by the development community, with the goal of improving the way Node.js works.
Given the fact Node.js is an extremely popular software, it has a big community of developers that are both using the software for their professional work, and giving their best to improve it, this is possible because Node.js is an open source project, which allows every person to have access to the code and modify it or propose fixes for any problem there might be.
Since the content inside the changelogs is written by developers as instructions for other developers, it is very common to find technical words and a lot of abbreviations being used, and even the strings that don’t have any abbreviations are written in a very concise way, always straight to the point.
This way, the developer reading the instructions cannot have any doubts about the changes that need to be applied in order to fix any bug that is affecting the software.
Discovering bugs and figuring out the solution is a job that deserves a proper recognition, this is why for every instruction that is proposed, there will always be the name or username of the developer that proposed said solution, all of this information is first posted using the Github platform, so besides the name of the developer, we will also find the Github links that are related to the issue in question.
Some examples of the instructions I translated can be seen below:
English
add regex check in test-buffer-bad-overload
Spanish
añadir chequeo de regex en test-buffer-bad-overload
This change was proposed because there was a condition (creating a buffer from a number) that should have triggered an error notification, but no error message was there. Therefore, a developer informed about the need to fix this little issue.
English
add second argument to assert.throws()
Spanish
añadir segundo argumento a assert.throws()
A developer realized that assert.throws() didn’t have a second argument even though this argument should be there, this is why he decided to inform the developing community about this issue and propose the solution.
English
avoid parsing division operator as regex
Spanish
evitar analizar operador de división como regex
The problem, in this case, was that some hashes were mistakenly interpreted as the beginning of a regular expression, this can cause some problems when executing code so a developer proposed an easy solution to bypass this issue.
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 59: 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!