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 74% of the project!

Translation Overview

For this occasion I translated two folders: Backporting-To-Release-Lines.md and Blocking-Vs-Non-Blocking.md

As the name implies, this module explains in an easy way how to backport* a pull request, what needs to be backported, what can be backported and how to submit a backport pull request.

*A backport is the action of making modifications to an old version of a software with contributions or patches originated in later versions.

This overview covers the difference between blocking and non-blocking calls in Node.js. This summary refers to the event loop and to libuv, but fortunately no prior knowledge of those topics is required.

Fortunately, too, the comparison is simple:

Blocking: operation are said to have blocking behavior if it waits for some event to get complete. For example: if a lock is not available a thread may enter a wait state on event till lock is available. Such an operation is said to be blocking.

Non-blocking: Non blocking behavior is like checking the condition at that instance. For example- in case of locks if it is not available it will not wait till it is available like blocking operation. Also we need to repeatedly check the availability of locks as there will be no callback like asynchronous calls.

As an example of the work done, I will use part of the section Concurrency and Throughput belonging to the Blocking-Vs-Non-Blocking.md module:

---

---

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 1214 words.
• I've translated a total of 102825 words so far*

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

To see my previous contributions in this project, check this!

• Zlib.md

Part 74

• Util.md

Part 73

• Domain.md

Part 72

• Domain-Module-Postmortem.md

Part 71

• Writing-tests.md

Part 70

• N-api.md.

From Part 62 to Part 69

• Timers-in-node.md

Part 61

• Maintaining-V8.md (v6.x)

Parts 59 and 60

• Net.md

Parts 57 and 58

• Onboarding.md

Part 56

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

Parts 54 and 55

• 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 (v10.x)

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.c