Spanish Translation of Node.js (Part 17) (1134 words)

Github Repository

https://github.com/nodejs/i18n

General Information & Project Details

- What is Node?

Node.js is is an environment in which you can run a program written in JavaScript (known as JS). Essentially, JS was made to run only through web browsers, which means that executing a JS program outside of a browser would normally throw an error. However, NodeJS took Chrome's V8 Runtime Engine for JavaScript and assambled it inside to allow for executing this language outside of a web browser.

The V8 Engine basically takes the JS code and converts it into a much faster machine code, which is a simpler low level code that the computer can execute without needing to first interpret it due to its simplicity and linear algorithmich structure.

Therefore, Node.js transforms your JS code into assembler-level machine code allowing you to use its capabilities as an scripting language, such as Python. This also allows you to basically take the functionalities available in languages like PHP and Ruby and apply them to JavaScript.

Contribution Specifications

- Translation Overwiew

In this part I worked on Stream, which is an interface to work with data streaming on Node due to the existance of a wide variety of streaming objects. They operate exclusively over strings and Buffer objects and are considered to be operated on the "Object Mode".

Part of this translation was focused on the diferent types o streams: Writable, Readable, Duplex and Transform. Every one of them accomplish specific functions. As it states, on the first type you can overwrite data, the second one are using to pass data to different sections of your program, Duplex can be both overwritten and read and the Transform type are capable of simultaneously rewriting and reading while modifying data.

Streams are hosted on the internal Buffer, from which you can recover the data, making it possible to limit the storage space of these same Buffers by specifying the maximum number of bytes for common streams and the maximum number of objects for those that are to be worked with on Object Mode.

In this section it draw my attention the use of the word buffering, since it doesn't have a direct translation on Spanish but we are to use a combination of words that together describe the data storage inside the Buffer.

- Languages

• Source Language: English
• Translated Language: Spanish

- Word Count

Number of words translated on this contribution: 1134 words, including a small number of coding instructions.

Proof of Authorship

The translation was submitted via CrowdIn and you can find all the related information on the following links.

Node.js Crowdin page

My Crowdin Profile
My Crowdin Activity
My Github Profile

- Examples sentences in Spanish:

• A key goal of the <0>stream</0> API, particularly the [<0>stream.pipe()</0>] method, is to limit the buffering of data to acceptable levels such that sources and destinations of differing speeds will not overwhelm the available memory.

  • Un objetivo clave de la API de <0>stream</0>, particularmente del método [<0>stream.pipe()</0>], es limitar el almacenamiento de datos en buffer a niveles aceptables, tales que las fuentes y destinatarios de diferentes velocidades no agoten la memoria disponible.

• Once the total size of the internal read buffer reaches the threshold specified by <0>highWaterMark</0>, the stream will temporarily stop reading data from the underlying resource until the data currently buffered can be consumed (that is, the stream will stop calling the internal <0>readable._read()</0> method that is used to fill the read buffer).

  • Una vez que el tamaño total del buffer de lectura interno alcanza el límite especificado por <0>highWaterMark</0>, el stream parará temporalmente de leer los datos desde el recurso subyacente, hasta que los datos almacenados en buffer actualmente se puedan consumir (es decir, el stream parará de llamar al método <0>readable._read()</0> interno que se utiliza para llenar el buffer de lectura).

• Because <0>Duplex</0> and <1>Transform</1> streams are both Readable and Writable, each maintain <2>two</2> separate internal buffers used for reading and writing, allowing each side to operate independently of the other while maintaining an appropriate and efficient flow of data.

  • Debido a que los streams <0>Dúplex</0> y <1>Transformador</1> son tanto Legibles como Escribibles, cada uno mantiene <2>dos</2> buffers internos separados utilizados para leer y escribir, lo que permite a cada lado operar independientemente del otro, mientras mantiene un apropiado y eficiente flujo de datos.

Previous Spanish translations for the project: