Nodo 2.png

Project Details

Nodo 1.png

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

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

Translation Overview

In this contribution I started 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.

A several number of the translated strings in this contribution explain the interactions that occur with events:

ENGLISH (1): During the [<0>'response'</0>][] event, one can add listeners to the
response object; particularly to listen for the <0>'data'</0> event..

SPANISH (1): Durante el evento [<0>'response'</0>][], se pueden añadir listeners al objeto de respuesta; particularmente para escuchar el evento <0>'data'</0> .

ENGLISH (2): The [<0>'response'</0>][] event is executed with one
argument which is an instance of [<0>http.IncomingMessage</0>][].

SPANISH (2): El evento [<0>'response'</0>][] se ejecuta con un
argumento que es una instancia de [<0>http.IncomingMessage</0>][].

ENGLISH (3): Note that when this event is emitted and handled, the [<0>'request'</0>][] event will
not be emitted.

SPANISH (3): Tenga en cuenta que cuando este evento sea emitido y manejado, el evento [<0>'request'</0>][] no será emitido.

ENGLISH (4): As with all <0>'error'</0> events, if no listeners
are registered the error will be thrown.

SPANISH (4): Como con todos los eventos <0>'error'</0>, si no hay listeners
registrados se arrojará el error.

I also translated a couple of strings that explain the different usages and descriptions of headers:

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

SPANISH (1): Utilice aquí una matriz de strings
si necesita enviar varios encabezados con el mismo nombre.

ENGLISH (2): If this header already exists
in the to-be-sent headers, its value will be replaced.

SPANISH (2): Si este encabezado ya existe
en los envíos de encabezados pendientes, su valor será reemplazado.

ENGLISH (3): Header names are not lowercased, and duplicates are not merged.

SPANISH (3): Los nombres de los encabezados no están en minúsculas, y los duplicados no están fusionados.

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

In object-oriented programming, protocols refer to the means by which unrelated objects communicate with each other.

Also, protocols are the description of:

The messages that an object comprehends.
The arguments through which these messages can be provided.
The types of results that these messages return.
The invariants that are preserved despite the modifications of any given object state.
The extraordinary situations that will require to be handled by the clients to the object.

References for this concept:

Words translated on this contribution, on http.md
Nodo 2.png

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