[Translation][Spanish] Node.js (1012 words) (Part 49)

in utopian-io •  2 months 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 #49 contribution to Node.js, on this occasion all of the strings I translated were from the commits section.

This type of string is always very similar because they always consist in brief instructions regarding changes that must be applied with the goal of improving the way Node.js is currently working.

The people who propose these changes are developers or other technical users that discover bugs or issues, and by using the GitHub platform, they are able to share with other developers the information about their findings, and propose what they think can be a good solution.

Since every person handling this information has some technical knowledge, it is very common to see some strings making references to other internal elements of the software, or simply using technical terms that aren’t very well know by the general public.

This means when a person is translating these strings, it is highly recommended to take the time and do some research on the technical terms in case there are doubts regarding the meaning of those words.

Below I added some examples of the strings I translated for this contribution:

English

add check for large strings

Spanish

añadir chequeo para strings grandes

This change was proposed because v8 only works with strings that can fit in an int, and sometimes, node.js’s n-api would specify a larger size, so to prevent any confusion and potential bugs in the future, a check was added to make sure the strings have the proper size.


English

stop creating references to primitives

Spanish

dejar de crear referencias a primitivos

A test was creating unnecessary references to primitives, the point of this test was to make sure “the finalize callback gets called when it should get called, that it gets called with the correct pointer, and that it does not get called when it should not get called. Creating persistent references is not necessary for verifying this.” Source To fix this little issue, a change was proposed, and eventually, applied.


English

add coverage for napi_typeof

Spanish

añadir cobertura para napi_typeof

There wasn’t a specific test that could evaluate napi_typeof in its entirely, therefore, a proposal was made to add a new test that could make sure everything was compatible and able to work without any issue.


When working on this contribution I was able to learn the following concept:

Primitives: in the context of coding and software, primitives are data that cannot be changed no matter what, in this sense it can be said they are as immutable as a blockchain. “In JavaScript, there are 6 primitive data types: string, number, boolean, null, undefined, symbol.” Source

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), and N-API.


  • 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

Part 49: 1012 words

Total: 54362 words

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 are good. It satisfies the requirements for a complete evaluation of your contribution.
  • The translated content fits the general meaning and use of the enlisted strings.
  • Thanks for explaining the dynamics of changelog commits, talking about the uses of various translated strings and sharing the definition of a few important terms you learnt while you were working on this collaboration. Your explanations were clear and useful.
  • You added some examples of the translated content in this report.
  • 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 UA account score is currently 4.498 which ranks you at #1965 across all Steem accounts.
Your rank has dropped 4 places in the last three days (old rank 1961).

In our last Algorithmic Curation Round, consisting of 191 contributions, your post is ranked at #159.

Evaluation of your UA score:
  • Some people are already following you, keep going!
  • The readers like your work!
  • Try to work on user engagement: the more people that interact with you via the comments, the higher your UA score!

Feel free to join our @steem-ua Discord server