This is my third contribution to Node.js. I’m currently translating this project into Spanish, along with an awesome group of translators and moderators from Utopian + Da Vinci, we are doing our best to do everything correctly. If you are interested in open-source projects, I encourage you to keep reading.
Repository
https://github.com/nodejs/i18n
Project Details
Node.js is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code outside of a browser. It achieves low latency and high throughput by taking a “non-blocking” approach to serving requests. Basically, Node.js can open, create, read, write, close and delete files on a server, using JavaScript. It also includes tasks that will be executed on certain servers.
I know it can be a bit confusing at first, so let me explain it to you in simpler words:
Let’s say you want to build a software to keep record of your company’s earnings. A feature where viewing your monthly earnings is updated live can be very useful. In that way, if one of your sales employees is busy, another employee could still be seeing the updates live, without reloading the page.
This has been done before using other technologies. However, Node.js is way faster and better. So, yes it’s pretty awesome for developers.
Contribution Specifications
Being such an important project, Node.js is being translated to several languages so it can reach many people around the world. As it for me, I am contributing to the Spanish language.
Translation Overview
During this contribution, I finished working on the folder dns.md, which basically explains the functionalities of the DNS module. The remaining part was a text called “Implementation considerations” (of the several functions inside this folder).
Here is a sample text with its translation:
English:
Although [dns.lookup()][] and the various dns.resolve*()/dns.reverse() functions have the same goal of associating a network name with a network address (or vice versa), their behavior is quite different. These differences can have subtle but significant consequences on the behavior of Node.js programs.
Spanish:
Aunque [dns.lookup()][] y las diversas funciones dns.resolve*()/dns.reverse() tienen el mismo objetivo de asociar un nombre de red con una dirección de red (o viceversa), su comportamiento es bastante diferente. Estas diferencias pueden tener sutiles pero significativas consecuencias en el comportamiento de los programas Node.js.
After I finished dns.md I started to work on perf_hooks.md, this folder explains the functionalities of the “Performance Timing API”.
Here is a sample text with its translation:
English:
The Performance Timing API provides an implementation of the W3C Performance Timeline specification. The purpose of the API is to support collection of high resolution performance metrics. This is the same Performance API as implemented in modern Web browsers.
Spanish:
La API de Timing del Rendimiento proporciona una implementación de la especificación Línea de Tiempo de Rendimiento de W3C. El propósito de la API es el de apoyar la colección de métricas de rendimiento de alta resolución. Este es el mismo Performance API que es implementado en navegadores Web modernos.
I also translated the classes: Performance, PerformanceEntry and PerformanceNodeTiming extends PerformanceEntry.
Since the text is related to computer science it is very important to do some research before translating a word if you are not sure about its meaning. As a matter of fact, some words were left untranslated on purpose, otherwise, their true meaning would be lost in the translation.
Languages
Source Language: English
Translated Language: Spanish
I have worked as a translator for the project Da Vinci Polyglot and I am currently working as a language moderator for the Utopian + Da Vinci translation category.
And of course, I am part of the Spanish team!
Word Count
I translated 1112 words on this contribution.
