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 35% 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 continue with the version 8.0.0, that is a new major version that includes a significant number of semi-major and semver-minor changes. For this contribution, I have translated only semver-minor commits. There's some examples:

English:

e3e56f1d71 - (SEMVER-MINOR) adding tests for initHooks API (Thorsten Lorenz) #12892

Spanish:

e3e56f1d71 - (SEMVER-MINOR) test: añadiendo pruebas para la API de initHooks (Thorsten Lorenz) #12892

Some asynchronous wrap providers were tested, as well as tests that show that hooks can be enabled/disabled within the events of their lives, and tests that verify the graph of resources triggering the creation of other resources.

Test helpers:

Test Helpers:

• init-hooks:

  • returns one collector instance
  • when created an async hook is created and the lifetime events are registered to call the appropriate collector functions
  • the collector also exposes enable and disable functions which call through to the async hook

• hook checks:

  • checks invocations of life time hooks against the actual invocations that were collected
  • in some cases like destroy a min/max range of invocations can be supplied since in these cases the exact number is non-deterministic

• verify graph:

  • verifies the triggerIds of specific async resources are as expected, i.e. the creation of resources was triggered by the resource we expect
  • includes a printGraph function to generate easily readable test input for verify graph
  • both functions prune TickObjects to create less brittle and easier to understand tests

---

English:

0432c6e91e - (SEMVER-MINOR) async_wrap: use double, not int64_t, for async id (Trevor Norris) #12892

Spanish:

0432c6e91e - (SEMVER-MINOR) async_wrap: usar double, no int64_t, para la id asíncrona (Trevor Norris) #12892

The number of ids is limited to 2^53-1 regardless of whether an int64_t is used or not because JS is limited to a double. So to make conversion simpler, track ids internally as a double. This will also make life simpler when this is eventually exposed to JS via a Float64Array.

---

English:

fe2df3b842 - (SEMVER-MINOR) async_wrap,src: add GetAsyncId() method (Trevor Norris) #12892

Spanish:

fe2df3b842 - (SEMVER-MINOR) async_wrap,src: añadir método de GetAsyncId() (Trevor Norris) #12892

In this commit, it is urged to allow the handles to retrieve their own uid's by adding a new method on the functiontemplates. Implementation of these into all other classes will come in a future commit. It's preferable that there be checks in there for these things, but a way of placing them hasn't been found that wouldn't be just as unreliable.

Test that checks all resources that can run getAsyncId() must be added.

Languages

This contribution was translated from English to Spanish.

Word Count

• In this contribution, I've translated 1337 words
• I've translated a total of 43090 words so far.

Previous translations on this project

• Part 35
• Part 34
• Part 33
• Part 32
• 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.