(Immagine made by @pab.ink)

This post is published in relation to the @utopian-io & @davinci.polyglot translation project, by a selected Translator for the Italian language

Project details and translation's reason

Node.js is a Javascript runtime. The project title refers to the node word, and indeed Node.js is closely related to this concept. It is a fascinating project and it has a considerable potential.
Below you can read some significant features of Node.js:

• Node.js is open source and takes full advantage of the power of communities to get better over time.
• Node.js relies heavily on the concept of scalability, in fact thanks to this feature it has the ability to generate network applications which also are based on the scalability.
• The concept of "events" in node is implemented and rethought, in fact the old concept used by other event library systems is replaced on Node with the event runtime. This "cycle of events" is activated through the calling process.
• Node.js is also designed to have an interface that makes it easy to use.
• Node distinguishes itself from other similar systems thanks to the absence of operating system threads.

These motivations are a great incentive to translate this project. Briefly I consider interesting two factors: the first one is how Nod.js differs from the majority of similar projects, the second one is its being completely open source. These two characteristics are so relevant that they stimulate me to translate it.

Github

Check out the whole project on Github

Contribution specification

My role as a translator consists in translating the strings I find during my translation work in the most appropriate way, from the English language to the Italian one.
This translation work is divided in two phases:
The first one is the work of simple translation and the second one consists in understanding the contexts and understand what kind of specific words should be translated and which not (for example because they are too technical to be translated).

Translation Overview

This is my 10th post related to the Node.js project: this is a project that is helping me to improve myself as a translator because it is full of new terms and I can state that for this reason it is very stimulating. In these days I translated about 1000 words belonging to different folders: the process.md folder (which I have completed), the process folder and the tracing.md folder (which is not yet completed). I have also translated the folder named string decoder.md. Below, to allow a better view both to my LM, and to anyone interested in my work as a translator, you can find the links of the folders:

• 1.) process.md

• 2.) string_decoder.md

• 3.) tracing.md

Excerpts of my work

Below I propose some significant strings that help to better understand the work I have done translating these 1000 words:

Process.md

Node.js will normally exit with a 0 status code when no more async operations are pending. The following status codes are used in other cases:
1 Uncaught Fatal Exception - There was an uncaught exception, and it was not handled by a domain or an ['uncaughtException'][] event handler.
2 - Unused (reserved by Bash for builtin misuse)
3 Internal JavaScript Parse Error - The JavaScript source code internal in Node.js's bootstrapping process caused a parse error. This is extremely rare, and generally can only happen during development of Node.js itself.
4 Internal JavaScript Evaluation Failure - The JavaScript source code internal in Node.js's bootstrapping process failed to return a function value when evaluated. This is extremely rare, and generally can only happen during development of Node.js itself.

string_decoder.md

String Decoder
Stability: 2 - Stable
The string_decoder module provides an API for decoding Buffer objects into strings in a manner that preserves encoded multi-byte UTF-8 and UTF-16 characters. It can be accessed using:
const { StringDecoder } = require('string_decoder');
The following example shows the basic use of the StringDecoder class.

tracing.md

Prior versions of Node.js required the use of the --trace-events-enabled flag to enable trace events. This requirement has been removed. However, the --trace-events-enabled flag may still be used and will enable the node, node.async_hooks, and v8 trace event categories by default.

Languages

Source language: English

Target language: Italian

To check my previous experiences as a translator you can consult my application

Word count

Words Translated: 1008.

Proof of authorship

You can lookup Crowdin project on the following link, as well as the summary of my activities

link 1
link 2