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

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

Translation Overview

In this contribution, I continued translating the second 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.

---

Just like in my last contribution, this time I also translated several strings that specify and describe interactions with headers:

ENGLISH (1): When using implicit headers (not calling [<0>response.writeHead()</0>][] explicitly), this property
controls the status message that will be sent to the client when the headers get
flushed.

SPANISH (1): Cuando se utilizan cabeceras implícitas (sin llamar a [<0>response.writeHead()</0>][] explícitamente), esta propiedad controla el código de estado que será enviado al cliente cuando
las cabeceras sean vaciadas.

ENGLISH (2): Attempting to set a header field name or value that contains invalid characters
will result in a [<0>TypeError</0>][] being thrown.

SPANISH (2): Intentar establecer un nombre de campo de cabecera o un valor que contenga caracteres inválidos dará como resultado al lanzamiento de un [<0>TypeError</0>][] .

ENGLISH (3): When the <0>'clientError'</0> event occurs, there is no <0>request</0> or <0>response</0>
object, so any HTTP response sent, including response headers and payload, <1>must</1> be written directly to the <0>socket</0> object.

SPANISH (3): Cuando el evento <0>'clientError'</0> ocurre, no hay ningún objeto de <0>request</0> o <0>response</0>, así que cualquier respuesta HTTP enviada, incluyendo las cabeceras de respuesta y la carga útil, <1>deben</1> ser escritas directamente al objeto de <0>socket</0> .

Examples of short sentences I translated:

ENGLISH (1): Flush the request headers.

SPANISH (1): Vaciar las cabeceras de solicitud.

ENGLISH (2): The request/response headers object.

SPANISH (2): El objeto de cabeceras de solicitud/respuesta.

ENGLISH (3): This event is emitted only once.

SPANISH (3): Este evento se emite solo una vez.

Server interaction was also very relevant regarding the information described by the strings:

ENGLISH (1): By default, the Server's timeout value is 2 minutes, and sockets are
destroyed automatically if they time out.

SPANISH (1): Por defecto, el valor de tiempo de espera del Servidor es 2 minutos, y los sockets se
destruyen automáticamente si se agota su tiempo de espera.

ENGLISH (2): However, if you assign a
callback to the Server's <0>'timeout'</0> event, then you are responsible for handling socket timeouts.

SPANISH (2): Sin embargo, si usted asigna un
callback al evento <0>'timeout'</0> del Servidor, entonces usted será responsable de manejar los tiempos de espera de los sockets.

ENGLISH (3): If there is a <0>'timeout'</0> event listener on the Server object, then it
will be called with the timed-out socket as an argument.

SPANISH (3): Si hay un listener del evento <0>'timeout'</0> en el objeto del Servidor, entonces
será llamado con el socket puesto en tiempo de espera como un argumento.

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

By definition, streams are a series of channels through which data flow. In technical terms, a stream is the logical link used by the programmer in C, C++ to read or write data from and to the standard devices connected to the PC. Generally, the standard device used to manipulate inputs is the keyboard, and in C++, it is associated with the cin object; the standard output device is (usually) associated with the screen or the monitor of the PC, and in C++, it can also be accessed via the cout object.

Streams can be used as the underlying data type for channels in interprocess communication.

The following image shows the standard streams for input, output and error:

References for this concept:

---

Words translated on my previous contribution, on http.md

Words translated on this contribution, 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.

Total of words translated so far: 40286.

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 18th, February 20th and February 21st.

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