[Translation][Spanish] Node.js (1212 words) (Part 69)

in utopian-io •  16 days 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.

lego.gif

Source

Contribution Specifications

  • Translation Overview

This is my 69# contribution to Node.js. The content I have been translating belongs to Node.js’s changelogs and the information we can find here is related to previous changes that were applied to Node.js in order to improve its performance, its documentation, its features, among other useful aspects.

All this information is originally written by developers from the global open source community that collaborate with the development of Node.js. This is one of the most positive aspects of having open source software, anyone can collaborate with the code and help in finding solutions to any bug or issue that could be affecting the software.

The platform that is used to manage the collaborations of all the developers is called GitHub, and it is through this platform that anyone can have access to the code and the last updates of Node.js. All of the changes are submitted using this platform, and once they are implemented the community is informed using this platform as well. Eventually, when it is time to request translations for other languages, it is the Crowdin platform the one that we use. So in short words, the information is first posted by the development community on GitHub, and later on, it is uploaded to Crowdin to facilitate the translations.

Below we can see a few examples of the instructions I translated.

English

fix compiler warning

Spanish

corregir la advertencia del compilador

A developer realized there was a little mistake in a compiler warning, and this mistake could cause some confusions or misinterpretations. Therefore, it was decided that a fix should be implemented as soon as possible to prevent any potential problem.


English

add emitExperimentalWarning

Spanish

añadir función de emitExperimentalWarning

This instruction consisted in adding a new warning that informed the user if he was using an experimental feature and that it could change at any time given the fact it is experimental. This way the users will be properly informed when using this type of feature.


English

fix typos in N-API

Spanish

corregir errores tipográficos en N-API

document.gif

Source

It is completely understandable to have a few typos when doing some writing, if the person doesn’t double check the writing it could very well have more than one typo. In this case, a developer realized there were some typos in N-API and he submitted his own correction to fix this mistake.

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 69: 1212 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

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Greetings, @dedicatedguy. Thanks for submitting your contribution!

  • The presentation and contents of your post 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 and discuss some more of the contents you worked on.
  • 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.
  • 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!