(Immagine made by @pab.ink)
Project details and translation's reason
Below you can read some significant features of Node.js:
1.) Node.js is open source and takes full advantage of the power of communities to get better over time.
2.) 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.
3.) 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.
4.) Node.js is also designed to have an interface that makes it easy to use.
5.) 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.
My role as a translator remains unchanged and consists in translating English words into Italian ones in the most appropriate way possible, trying to create the maximum harmony between English and its translation into Italian.
This is my first post of the translation of Node.js. project. Talking about informatics, Node.js is similar to the projects I have translated previously, but which obviously requires great commitment and attention, as we are talking about a very technical project.
I am grateful for this great opportunity that has been given to me because it will help me to improve myself and test myself on further new projects.
Today I translated part of the folder Net.dm, (to facilitate the readers and my LM, I wrote up here the link of the folder)
In these thousand words I found numerous topics and new terms like: Listener (a term used in JAVA script) which is a term that acquires both a noun and a verb function and requires attention in its contextualization, another very recurring term in this folder is handle (also a very common term in JAVA) and in addition I found the terms path and port.
The folder is mainly based on these listed points.
Excerpts of my work
Below I propose some significant strings that help to better understand the work I have done translating these 1038 words:
This happens when another server is already listening on the requested <0>port</0> / <0>path</0> / <0>handle</0>.
One way to handle this would be to retry after a certain amount of time:
Start a server listening for connections on a given <0>handle</0> that has already been bound to a port, a UNIX domain socket, or a Windows named pipe.
The <0>handle</0> object can be either a server, a socket (anything with an underlying <0>_handle</0> member), or an object with an <0>fd</0> member that is a valid file descriptor.
new net.Server([options][, connectionListener])
See [<0>net.createServer([options][, connectionListener])</0>][<0>net.createServer()</0>].
The last parameter <0>callback</0> will be added as a listener for the [<0>'listening'</0>] event.
The same applies when the path was created by a Node.js API but the program crashes abruptly.
It gets truncated to <0>sizeof(sockaddr_un.sun_path) - 1</0>, which varies on different operating system between 91 and 107 bytes.
The path <0>must</0> refer to an entry in <1>\?\pipe</1> or <1>\.\pipe</1>.
Source language: English
Target language: Italian
To check my previous experiences as a translator you can consult my application
Word count: 1078
Proof of authorship
You can lookup Crowdin project on the following link, as well as the summary of my activities