Translation report: process.md of Node.js (words 1013)
(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 eighth post for the Node.js. project.
In this translation I dealt with the folder named process.md (translating 1000 words, I completed about 62% of the file). As you can understand from the name of the folder, its main topic is the process. In particular I found arguments such as: the code exit and the warnings which are located in different contexts.
Node.js is rather a technical project and I have often found also numerous pure computer strings. I am grateful for this opportunity that allows me to always learn new notions.
Excerpts of my work
Below I propose some significant strings that help to better understand the work I have done translating these 1000 words:
Code exit...
a.)
code {integer} The exit code. Default: 0.
The process.exit() method instructs Node.js to terminate the process synchronously with an exit status of code. If code is omitted, exit uses either the 'success' code 0 or the value of process.exitCode if it has been set. Node.js will not terminate until all the ['exit'] event listeners are called.
b.)
The shell that executed Node.js should see the exit code as 1.
Calling process.exit() will force the process to exit as quickly as possible even if there are still asynchronous operations pending that have not yet completed fully, including I/O operations to process.stdout and process.stderr.
Warnings...
As a best practice, warnings should be emitted only once per process. To do so, it is recommended to place the emitWarning() behind a simple boolean flag as illustrated in the example below:
Languages
Source language: English
Target language: Italian
To check my previous experiences as a translator you can consult my application
Word count
Words Translated: 1013
Proof of authorship
You can lookup Crowdin project on the following link, as well as the summary of my activities
Hi @filippocrypto.
Congratulations on another great contribution. Your translation work was, as usual, very good. I’m looking forward to your next contribution.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Chat with us on Discord
Thank you for your review, @imcesca! Keep up the good work!
Hi @filippocrypto!
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server
Hey, @filippocrypto!
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!