Node.js Translation to Spanish - 1042 words (Part 34)

Hello, this is my 34th open source contribution for Utopian and DaVinci as translator. I have been translating different Node.js Files during the past few months. This time, I continued translating "process.md" file, because it is a very interesting part of all Node.js because it is a control tool that improve the perforance of each process.

I work with an extensive team of translators team whose performance has been excellent. By this time a 38% of this huge project has been translated in a few months; yes, a million words project being translated that fast. I must say that I'm very excited about that.

I invite you to read this post because it is a knowledge font that provides tools for the people who are working with Node.js or any other open source project development. I hope this contribution is useful.

It looks difficult to understand at first, but let me explain it with the next example.

Imagine that you have been developing a new android app that uses the APIs from Google Maps and Twitter. When testing the app, you realize that both APIs are written in different languages and you must change one of them to make it work, but that's a lot of work and goes against the reasons to use an API. Node.js is the solution to problems like this because it allows the union between different programming languages without affecting its performance.

I decided to translate this project because I'm an engineering student and innovation is my passion; I love creating solutions to problems like this. Also, I like sharing information and a way to do it is translating the content of a big project like this so people around the world can access to it and share it too.

In this part of the file there were a lot of new concepts that are part of the warnings in Node.js object process. It has a lot of methods and internal objects that make this object very useful for every Node.js process. I know this event looks very simple and with limited functions, nonetheless, because of its settings it is great. There was also a new event introduced, the signal events. Those events "will be emitted when the Node.js process receives a signal.", this means that are informative events that alert the entire process what action must be taken after receiving a signal.

When a signal is emitted, a handler will take it as its first argument so the handler can work in the process with a specific instruction, given by the signal.

The following are some of the signal that could be emitted (the signals are followed by their function or meaning):

The original language of this change log is English and it was translated into Spanish, which is my native language. I have experience translating in projects like Loopring wallet and Yapbam. These projects make me grow and learn a lot about open source projects.

You can visit my profile (navx) on Crowdin's website to find proof of authorship. Also, you can visit the Activity tab in the Node.js project and filter my contributions between December 10th and December 12th, which were the dates of the translation and the corrections respectively.