Node.js Translation to Spanish - ( 1254 words) (Part-77)

cremisi(66)

Published in

#utopian-io

Words

647

Reading

3 min

Listen

Play

alt

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.

Node.js came into existence when the original developers of JavaScript extended it from something you could only run in the browser to something you could run on your machine as a standalone application.

In simple words, it's an open source execution environment for developing web applications, which is event-based, it uses the V8 engine to provide an execution environment that compiles and executes JavaScript at a higher speed. It is possible to run Node.js without any restriction on Windows, Linux and Mac OS X.

It should be noted that it is NOT a server language, this means that it executes code, so it could be understood as an interpreter.

Contribution Specifications

Node.js is currently being translated into 33 languages. I'm contributing to translate it into the Spanish language.

So far, we have managed to translate 75% of the project!

Translation Overview

For this occasion I translated the folder Zlib.md. The zlib module provides compression functionality implemented using Gzip and Deflate/Inflate.

It's ironic how we are talking about compressing and I had to use a program to compress this GIF because it was really very heavy but I really wanted to place it here.

Zlib provides facilities for control of processor and memory use. A compression level value may be supplied that trades-off speed with compression. There are also facilities for conserving memory, useful in restricted memory environments such as some embedded systems.

The zlib module can be used to implement support for the gzip and deflate content-encoding mechanisms defined by HTTP. As an example of the work done, I will use part of the section Compressing HTTP requests and responses:

English:

Compressing HTTP requests and responses

The HTTP [Accept-Encoding][] header is used within an http request to identify the compression encodings accepted by the client. The [Content-Encoding][] header is used to identify the compression encodings actually applied to a message.

Note: Using zlib encoding can be expensive, and the results ought to be cached. See Memory Usage Tuning for more information on the speed/memory/compression tradeoffs involved in zlib usage.

Spanish:

Comprimir solicitudes y respuestas HTTP

La cabecera HTTP [Accept-Encoding][] se usa dentro de una solicitud http para identificar las codificaciones de compresión aceptadas por el cliente. La cabecera [Content-Encoding][] se utiliza para identificar las codificaciones de compresión realmente aplicadas a un mensaje.

Nota: Utilizar codificación basada en zlib puede resultar costosa y los resultados deben ser almacenados en caché. Vea Ajustes en el Uso de Memoria para obtener más información sobre las operaciones en velocidad/memoria/compresión involucradas en el uso de zlib.