Node.js Translation to Spanish - (1200 words) (Part 45)

in utopian-io •  2 months 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. So far, we have managed to translate 45% of the project.

Translation Overview

I continue with the ChangeLog_V7.md folder

In my previous contributions, I explained what a change log is about. 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.

image.png

During this contribution, I finished translating the commits belonging to the version 7.7.4 and I started with the versions 7.7.3, 7.7.2, 7.7.1 and 7.7.0.

Examples:

Version 7.7.3

English:

a6539ece2c - assert: optimize code path for deepEqual Maps (Ruben Bridgewater) #14501

Spanish:

a6539ece2c - assert: optimizar la ruta del código para deepEqual Maps (Ruben Bridgewater) #14501

This improves the performance for maps with object keys and for deepEqual loose equal primitive keys that contain primitives as value. The first part decreases the performance of the common case a tiny bit (primitive keys) in favor of the much slower worst case. Even though the common case must do a typecheck more, it's better to read that way.


Version 7.7.1:

English:

02260eab98 - test,doc: make module name match gyp target name (Gabriel Schulhof) #15209

Spanish:

02260eab98 - test,doc: hacer que el nombre del módulo coincida con el nombre de destino de Gyp (Gabriel Schulhof) #15209

Currently, the nm_modname does not match the file name of the resulting
module. This seeks to introduce some consistency into the nm_modname property by having the name of the module appear in exactly one place: the target_name property of the gyp target that builds the module.

Languages

This contribution was translated from English to Spanish.

Word Count

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

Previous translations on this project

From Part 41 to Part 44

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

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

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Greetings, @cremisi. Thanks for submitting your contribution!

  • The presentation and contents of your post are good and satisfy the requirements for a complete evaluation of your contribution. Nice formatting to keep track of your past reports.
  • 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 explained the composition of a couple strings you translated in a very clear way. Please consider adding a little more data about your works in the upcoming contributions.
  • You shared several examples of your translations on the folder you worked on.

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!

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