[Translation][Spanish] Node.js (1210 words) (Part 63)

in #utopian-io5 years ago

Source

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 63# contribution to Node.js. After this contribution, the Node.js project is 64% completed for the Spanish language. There still close to 1/3 of the project text that still needs to be translated, and in the Spanish team we are working together to successfully complete the entire project.

Regarding this particular contribution, the strings I translated were all from Node.js’s changelogs, which contains each and every single change that has been applied to this software, categorized by versions.

This information originally comes from GitHub, which is where the developer community share their work with the goal of improving the way Node.js works and solve any issue or bug that might arise. It is important to notice that the only reason why developers from all over the world can make their own contributions is because this software is completely open source. This allows any person to have access to the source code and experiment with it as they wish.

When it comes to the strings I translated, the majority of them consist in simple instructions about fixing some technical error or simply about fixing information from Node.js documents. As I mentioned before, given the fact this information comes from GitHub we will always find in the strings containing instructions a link to the original commit from GitHub, the name of the developer who proposed that change, and the link to the merged pull-request also from GitHub.

Below we can see a few examples of the kind of instructions I translated for this contribution:

English

fix test-vm-sigint flakiness

Spanish

reparar defectuosidad de test-vm-sigint

There was a little issue where a signal from a child process had the risk of not being properly handled because the corresponding handler was not previously set. This could result in the process acting erroneously.

modern development.gif

Source


English

fix memory leaks in inspector tests

Spanish

reparar fugas de memoria en pruebas de inspector

The problem in this case was that the inspector tests “weren't closing open libuv handles properly” Source and this was causing some complications. Luckily a developer discovered this bug and informed the community about how to fix it.


English

disable Ctrl+C support on win32 for now

Spanish

deshabilitar soporte de Ctrl+C en win32 por ahora

There was an issue that was being triggered by using REPL commands with Ctrl+C support, the actual cause of this issue wasn’t related to Ctrl+C support but for some reason, these commands were triggering the bug. Therefore, it was recommended to disable them in order to carry out deeper research.

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 63: 1210 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:

Proof of Authorship

My activity on Crowdin

Sort:  

Greetings, @dedicatedguy. Thanks for submitting your contribution!

  • The presentation and contents of your post are good and satisfy the requirements for a complete evaluation of your contribution.
  • Thanks for explaining the dynamics of changelog commits and talking about the importance of various strings you addressed. Nice personalization of your report, we invite you to keep on your creativity.
  • You added various examples of the content you translated in this contribution.
  • The translated content fits coherently the general meaning and use of the referred strings and you did a precise use of the terminology of the project.

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!

Coin Marketplace

STEEM 0.18
TRX 0.15
JST 0.028
BTC 63283.09
ETH 2463.49
USDT 1.00
SBD 2.54