Source

Node.js's Github Repository

Project Details

Node.js is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code outside the browser.

Node.js brings event-driven programming to web servers, enabling development of fast web servers in JavaScript. Developers can create highly scalable servers without using threading, by using a simplified model of event-driven programming that uses callbacks to signal the completion of a task. Node.js connects the ease of a scripting language (JavaScript) with the power of Unix network programming.

In easier to understand words: Node-js is a free platform whose goal is to provide its users the possibility to create lightweight and cost efficient web servers, how does Node.js do this?

Node.js handles web server connections in a way so they don´t take up as much space in a server, and thus, the owner of a project would not need to invest as much money in multiple servers to store so much information in Gigabytes.

Being an Open Source Project, Node.js possesses immense value for providing so much while at the same time being totally free.

Contribution Specifications

570,838 words have been translated so far in the Spanish folder of Node.js, which amounts to a total of 54% done in regards to the completion of the translation of this big project.

Translation Overview

In this contribution, I started translating the third http.md folder of Node.js.

"HTTP" stands for "Hypertext Transfer Protocol", which refers to the communication protocol that allows information transfers to occur within the World Wide Web. HTTP was developed by the World Wide Web Consortium and the Internet Engineering Task Force, a partnership that ended in 1999.

HTTP defines the syntaxis and the semantics that utilize the software elements of web architecture (clients, servers, proxies) to communicate.

HTTP is a stateless protocol, which means that it doesn't save any information regarding previous connections.

---

In this contribution I found numerous strings that reference timeout values:

ENGLISH (1): <0>timeout</0> {number}: A number specifying the socket timeout in milliseconds.

SPANISH (1): <0>timeout</0> {number}: Un número que especifica el tiempo de espera del socket en milisegundos.

ENGLISH (2): If a handler is assigned to the request, the response, or the server's <0>'timeout'</0> events,
timed out sockets must be handled explicitly.

SPANISH (2): Si se asigna un handler a la solicitud, la respuesta, o a los eventos <0>'timeout'</0> del servidor,
los sockets sin tiempo de espera deberán ser manejados de manera explícita.

ENGLISH (3): A value of <0>0</0> will disable the timeout behavior on incoming connections.

SPANISH (3): Un valor de <0>0</0> inhabilitará el comportamiento del tiempo de espera en conexiones entrantes.

Examples of short sentences I translated:

ENGLISH (1): Defaults to 5000 (5 seconds).

SPANISH (1): Por defecto su valor es 5000 (5 segundos).

ENGLISH (2): {number} Timeout in milliseconds.

SPANISH (2): {number} Tiempo de espera en milisegundos.

ENGLISH (3): Reference to the underlying socket.

SPANISH (3): Referencia al socket subyacente.

The last concepts that I consider relevant to be included in today's report are array values and interactions:

ENGLISH (1): Use an array of strings here to send multiple headers with the same name.

SPANISH (1): Aquí, utiliza una matriz de strings para enviar varias cabeceras con el mismo nombre.

ENGLISH (2): Since a shallow copy is used, array values may be mutated without additional calls to various header-related http module methods.

SPANISH (2): Ya que se utiliza una copia superficial, los valores de la matriz pueden ser mutados sin llamadas adicionales a varios métodos del módulo http relacionados con la cabecera.

ENGLISH (3): Returns an array containing the unique names of the current outgoing headers.

SPANISH (3): Devuelve una matriz que contiene los nombres únicos de las cabeceras salientes actuales.

In this contribution, the new concept I learned about while working on this subfolder was Handler:

In computer programming, an event handler is a callback subroutine that handles inputs received in a program (called a listener in Java and JavaScript).

Each event is a piece of application-level information from the underlying framework, typically the GUI toolkit. GUI events include key presses, mouse movement, action selections, and timers expiring.

On a lower level, events can represent availability of new data for reading a file or network stream.

Handlers are a central concept in event-driven programming.

The first step in developing an event-driven program is to write a series of subroutines, or methods, called event-handler routines. These routines handle the events to which the main program will respond. For example, a single left-button mouse-click on a command button in a GUI program may trigger a routine that will open another window, save data to a database or exit the application.

References for this concept:

---

Words translated so far on http.md

Here's the link to the http.md folder:

Languages

The project's source language is English and it is being translated into Spanish.

Also, Node.js is currently being translated into other 32 languages. I´m contributing to making this project accessible to the Spanish speaking community online.

Besides collaborating as a translator for Open Source Projects on Crowdin I also work as a Freelance Translator for a law firm in the US, I've been working for that company for one year and two months, translating sworn statements and legal documents from English to Spanish and viceversa.

Open Source Projects I've worked on and contributed to as a translator:

1 . Verdaccio

2 . OroCRM

3 . BiglyBT

4 . The Curious Expedition

5 . Node.js

Word Count

Part 1: 1016; Part 2: 1026; Part 3: 1035; Part 4: 1092; Part 5: 1050; Part 6: 1147; Part 7: 1133; Part 8: 1049; Part 9: 1090; Part 10: 1093; Part 11: 1024; Part 12: 1102; Part 13: 1085; Part 14: 1049; Part 15: 1035; Part 16: 1059; Part 17: 1041; Part 18: 1114; Part 19: 1114; Part 20: 1033; Part 21: 1030; Part 22: 1059; Part 23: 1047; Part 24: 1070; Part 25: 1151; Part 26: 1039; Part 27: 1025; Part 28: 1035; Part 29: 1063; Part 30: 1037; Part 31: 1047; Part 32: 1023; Part 33: 1041; Part 34: 1064; Part 35: 1060; Part 36: 1052; Part 37: 1055; Part 38: 1064; Part 39: 1066.

Total of words translated so far: 41352.

Proof of Authorship

Node.js on Crowdin:

Node.js's Translation Report:

Activity on Node.js:

My Crowdin Profile:

This translation contribution was submitted via Crowdin on February 26th and February 27th.

For further Proof of Authorship in regards to this contribution you can see my activity on Crowdin here.