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 32% of the project.
Translation Overview
I continue with my contribution in the ChangeLog_V8.md folder.
A Changelog is a record of all the notable changes made to a project, it usually includes change records such as new features or bug fixes. It includes all the changes historically, although it is intended that a Changelog does not include all the changes, but rather it contains a list of notable changes ordered chronologically for each version of a project.
For large projects, there are many people who work in systems with different ideas about design and different knowledge about standards. This leads to a totally different technique, and the more documented it is, the more people can work together.
I've finished translating the commits of version 8.2.0, I translated the only three commits of version 8.1.4 and started version 8.1.3.
The most notable change of version 8.1.4 was:
- V8 Snapshots Disabled
The hashseed embedded in the snapshot is currently the same for all executions of the binary. This opens node to collision attacks that could result in a Denial of Service. Snapshots have been temporarily disabled until a more robust solution is found. The only three commits of this version support this same purpose.
Here the translated commits:
English:
51d69d2bec - build: disable V8 snapshots (Ali Ijaz Sheikh)
d70fac47af - deps: cherry-pick 9478908a49 from cares upstream (David Drysdale)
803d689873 - test: verify hash seed uniqueness (Ali Ijaz Sheikh)
Spanish:
51d69d2bec - build: deshabilitar snapshots de V8 (Ali Ijaz Sheikh)
d70fac47af - deps: hacer cherry-pick a 9478908a49 desde upstream de cares (David Drysdale)
803d689873 - test: verificar la singularidad de la hash seed (Ali Ijaz Sheikh)
Regarding version 8.1.3, two regressions in the stream
module were solved:
The
finish
event will now always be emitted after theerror
event if one is emitted.In object mode, readable streams can now use
undefined
again.
Some commits:
English:
0bb53a7aa2 - doc: make socket IPC examples more robust (cjihrig) #13196
Spanish:
0bb53a7aa2 - doc: hacer que los ejemplos de IPC de sockets sean más robustos (cjihrig) #13196
This commit aims to improve the documentation examples that send sockets over IPC channels. Specifically, pauseOnConnect is added to a server that inspects the socket before sending and a 'message' handler adds a check that the socket still exists.
English:
0a9e96e86c - stream: finish must always follow error (Matteo Collina) #13850
Spanish:
0a9e96e86c - stream: "finish" debe seguir siempre a "error" (Matteo Collina) #13850
When _write completes with an Error, finish
was emitted before error
if the callback was asynchronous. This commit restore the previous behavior.
The logic is still less then ideal, because we call the write() callback before emitting error if asynchronous, but after if synchronous. This commit do not try to change the behavior.
Languages
This contribution was translated from English to Spanish.
Word Count
- In this contribution, I've translated 1329 words
- I've translated a total of 37842 words so far.
Previous translations on this project
- Part 31
- Part 30
- Part 29
- Part 28
- Part 27
- Part 26
- Part 25
- Part 24
- Part 23
- Part 22
- Part 21
- Part 20
- Part 19
- Part 18
- Part 17
- Part 16
- Part 15
- Part 14
- Part 13
- Part 12
- Part 11
- Part 10
- Part 9
- Part 8
- Part 7
- Part 6
- Part 5
- Part 4
- Part 3
- Part 2
- Part 1
Proof of Authorship
You can check My Crowdin Profile for verify my contribution in this project.