(Immagine made by 
This post is published in relation to the 
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.
Check out the whole project on Github
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).
This is my seventh post for the Node.js. project. For every translation I always learn new terms and new topics and I can state that this is a very positive thing that allows me to increase my knowledge, being Node.js a rather technical project. For this reason I am very glad to have this opportunity.
With this translation work I have faced arguments that I had already seen in the last one like the listeners and the call, and other terms that I had already faced like the warnings. But I found also a new topic, the signals, that can be found in different contexts. The folder I dealt with is named proces.md, which I have not completed yet: I translated 38% of this folder, about 3000 words out of 7000.
Below I propose some significant strings that help to better understand the work I have done translating these 1000 words:
Signal events will be emitted when the Node.js process receives a signal.
Please refer to signal(7) for a listing of standard POSIX signal names such as 'SIGINT', 'SIGHUP', etc.
The signal handler will receive the signal's name ('SIGINT', 'SIGTERM', etc.) as the first argument.
The name of each event will be the uppercase common name for the signal (e.g. 'SIGINT'for SIGINT signals).
'SIGKILL' cannot have a listener installed, it will unconditionally terminate Node.js on all platforms'SIGSTOP' cannot have a listener installed.'SIGBUS', 'SIGFPE', 'SIGSEGV' and 'SIGILL', when not raised artificially using kill(2), inherently leave the process in a state from which it is not safe to attempt to call JS listeners. Doing so might lead to the process hanging in an endless loop, since listeners attached using process.on() are called asynchronously and therefore unable to correct the underlying problem.
By default, Node.js will print process warnings to stderr.
The --no-warnings command-line option can be used to suppress the default console output but the 'warning' event will still be emitted by the process object.
The following example illustrates the warning that is printed to stderr when too many listeners have been added to an event:
Source language: English
Target language: Italian
To check my previous experiences as a translator you can consult my application
Words Translated: 1011
You can lookup Crowdin project on the following link, as well as the summary of my activities
