Node.js Translation to Spanish - (1122 words) (Part-68)

in #utopian-io6 years ago

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.

image.png

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

Translation Overview

I started the translation of the folder N-api.md.

1_qwoA9FmZDrE5q_9qqBCQ.png

N-API (pronounced N as in the letter, followed by API) is an API for building native Addons. It is independent from the underlying JavaScript runtime (ex V8) and is maintained as part of Node.js itself.

Previously, I briefly explained what an API is. If you want to see more information about it, you can visit this post.

The N-API is an API that ensures ABI stability across Node.js versions and different compiler levels. And an ABI (application binary interface) it's the interface between two program modules, it determines details such as how to call functions, in which binary format information should be passed from one program component to the next, or to the operating system in the case of a system call.

In this part of the module the envelope of objects and their functions is explained.

N-API offers a way to "wrap" C++ classes and instances so that the class constructor and methods can be called from JavaScript.

  • The [napi_define_class][] API defines a JavaScript class with constructor, static properties and methods, and instance properties and methods that correspond to the C++ class.
  • When JavaScript code invokes the constructor, the constructor callback uses [napi_wrap][] to wrap a new C++ instance in a JavaScript object, then returns the wrapper object.
  • When JavaScript code invokes a method or property accessor on the class, the corresponding napi_callback C++ function is invoked. For an instance callback, [napi_unwrap][] obtains the C++ instance that is the target of the call.

For wrapped objects it may be difficult to distinguish between a function called on a class prototype and a function called on an instance of a class. A common pattern used to address this problem is to save a persistent reference to the class constructor for later instanceof checks.

As an example of the work done, I will use the function napi_wrap belonging to this module:


English:

napi_wrap

Wraps a native instance in a JavaScript object. The native instance can be retrieved later using napi_unwrap().

When JavaScript code invokes a constructor for a class that was defined using napi_define_class(), the napi_callback for the constructor is invoked. After constructing an instance of the native class, the callback must then call napi_wrap() to wrap the newly constructed instance in the already-created JavaScript object that is the this argument to the constructor callback. (That this object was created from the constructor function's prototype, so it already has definitions of all the instance properties and methods.)

Typically when wrapping a class instance, a finalize callback should be provided that simply deletes the native instance that is received as the data argument to the finalize callback.

The optional returned reference is initially a weak reference, meaning it has a reference count of 0. Typically this reference count would be incremented temporarily during async operations that require the instance to remain valid.

Caution: The optional returned reference (if obtained) should be deleted via [napi_delete_reference][] ONLY in response to the finalize callback invocation. (If it is deleted before then, then the finalize callback may never be invoked.) Therefore, when obtaining a reference a finalize callback is also required in order to enable correct proper of the reference.

Spanish:

napi_wrap

Envuelve una instancia nativa en un objeto de JavaScript. La instancia nativa puede ser recuperada luego utilizando napi_unwrap().

Cuando un código de JavaScript invoca un constructor para la clase que fue definida utilizando napi_define_class(), el napi_callback para el constructor es invocado. Luego de construir una instancia de la clase nativa, la callback debe llamar entonces a napi_wrap() para envolver a la instancia recién construida en el ya creado objeto de JavaScript que es el argumento this de la callback del constructor. (Ese objeto this fue creado desde el prototype de la función del constructor, entonces ya tiene definiciones de todas las propiedades y métodos de instancia.)

Normalmente, al envolver una instancia de clase, se debe proporcionar un callback de terminación que simplemente elimine la instancia nativa que se recibe como el argumento data para la callback de terminación.

La referencia opcional devuelta es, inicialmente, una referencia débil, lo que significa que tiene una cuenta de referencia de 0. Normalmente, esta cuenta de referencia se incrementará temporalmente durante operaciones asíncronas que requieran que la instancia permanezca válida.

Precaución: La referencia opcional devuelta (si se obtiene) debe ser eliminada a través de [napi_delete_reference][] SOLO en respuesta a la invocación de la callback de terminación. (Si es eliminada antes de eso, entonces puede que la callback de terminación nunca sea invocada.) Por lo tanto, cuando se obtiene una referencia, también se requiere una callback de terminación para permitir la apropiada corrección de la referencia.


Note: This API may modify the prototype chain of the wrapper object. Afterward, additional manipulation of the wrapper's prototype chain may cause napi_unwrap() to fail.

Languages

This contribution was translated from English to Spanish.

Word Count

The number of words reflected in the title doesn't include words that didn't require a translation.

  • In this contribution, I've translated 1122 words.
  • I've translated a total of 91004 words so far*

*Considering non-translatable content (proper names, functions, codes, etc.)

Previous translations on this project

From Part 62 to Part 67

Part 61

Parts 59 and 60

Parts 57 and 58

Part 56

Parts 54 and 55

Part 53

Part 52

From Part 41 to Part 51

From Part 14 to Part 40

Part 13

Parts 11 and 12.

From Part 7 to Part 10

From Part 1 to Part 6

Proof of Authorship

image.png

This counter includes non-translatable words, so it is necessary to work on more content to extract an average of 1000 translatable words.

You can check My Crowdin Profile for verify my contribution in this project.

Sort:  

Greetings, @cremisi. Thanks for submitting your contribution!

  • The presentation and contents of your post satisfy the requirements for a complete evaluation of your contribution.
  • You did a precise use of the terminology involved in this translation.
  • The translated content fits coherently the general meaning and use of the addressed strings.
  • You shared examples of the translations on the folder you worked on.
  • You explained the contents of the translated folder in a very clear way.
  • You are invited to show some more of your personal touch on the future reports. Keep it up!

Congratulations on this collaboration!

Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.

To view those questions and the relevant answers related to your post, click here.


Chat with us on Discord

Thank you for your review, @alejohannes! Keep up the good work!

Congratulations @cremisi! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :

You published more than 70 posts. Your next target is to reach 80 posts.

You can view your badges on your Steem Board and compare to others on the Steem Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

To support your work, I also upvoted your post!

Vote for @Steemitboard as a witness to get one more award and increased upvotes!

Hi @cremisi!

Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server

Hey, @cremisi!

Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!

Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).

Want to chat? Join us on Discord https://discord.gg/h52nFrV.

Vote for Utopian Witness!