Node.js Translation to Spanish - (1135 words) (Part-55)

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 came into existence when the original developers of JavaScript extended it from something you could only run in the browser to something you could run on your machine as a standalone application.

In simple words, it's an open source execution environment for developing web applications, which is event-based, it uses the V8 engine to provide an execution environment that compiles and executes JavaScript at a higher speed. It is possible to run Node.js without any restriction on Windows, Linux and Mac OS X.

It should be noted that it is NOT a server language, this means that it executes code, so it could be understood as an interpreter.

Contribution Specifications

Node.js is currently being translated into 33 languages. I'm contributing to translate it into the Spanish language.

So far, we have managed to translate 56% of the project!

Translation Overview

In my previous contribution, I started translating the folder "event-loop-timers-and-nexttick.md" and with this contribution I finished the folder. I mentioned that I loved that it had little "non-translatable" content, but it turned out that it was just the beginning and in this part there were SO MANY words that I could not translate.

This module deals with what is the Node.js event loop. In the previous post I also mentioned the order of operations of the event loop and I added a diagram that I will put back here, but this time the phases are explained in detail.

A timer specifies the threshold after which a provided callback may be executed rather than the exact time a person wants it to be executed. Timers callbacks will run as early as they can be scheduled after the specified amount of time has passed; however, Operating System scheduling or the running of other callbacks may delay them.

This phase executes callbacks for some system operations. For example, if a socket receives an error when it tries to connect, some systems must wait to report the error. This will be queued to execute in the I/O callback phase.

Only used internally.

The poll phase has two main functions: executing scripts for timers whose threshold has elapsed, then processing events in the poll queue.
When the event loop enters the poll phase and there are no timers scheduled, one of two things will happen:

• If the poll queue is not empty, the event loop will iterate through its queue of callbacks executing them synchronously until either the queue has been exhausted, or the system-dependent hard limit is reached.
• If the poll queue is empty, the event loop will check for timers whose time thresholds have been reached. If one or more timers are ready, the event loop will wrap back to the timers phase to execute those timers' callbacks.

This phase allows a person to execute callbacks immediately after the poll phase has completed. If the poll phase becomes idle and scripts have been queued, the event loop may continue to the check phase rather than waiting.

If a socket or handle is closed abruptly, the 'close' event will be emitted in this phase.

Personally, there weren't many terms that I wasn't familiar with, so the whole process of the event loop was really simple to understand and translate. I leave some examples of the translation:

English:

Spanish:

English:

Spanish:

---

Languages

This contribution was translated from English to Spanish.

Word Count

The number of words reflected in the title doesn't include words that didn't require a translation.

• In this contribution, I've translated 1135 words.
• I've translated a total of 72416 words so far*

*Considering non-translatable content (proper names, functions, codes, etc.)

Previous translations on this project

• Event-loop-timers-and-nexttick.md

Part 54

• VM.md

Part 53

• Building-node-with-Ninja.md

Part 52

• ChangeLog_V7.md

From Part 41 to Part 51

• ChangeLog_V8.md

From Part 14 to Part 40

• Using-Internal-Errors.md and Building-Node-with-Ninja.md

Part 13

• Maintaining-V8.md

Parts 11 and 12.

• Pull-requests-md

From Part 7 to Part 10

• TLS.md

From Part 1 to Part 6

Proof of Authorship

This counter includes non-translatable words, so it is necessary to work on more content to extract an average of 1000 translatable words.

You can check My Crowdin Profile for verify my contribution in this project.