Node.js Translation to Spanish - (1117 words) (Part 38)
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 40% 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-patch commits. There's some examples:
English:
972bfe1514 - n-api: Sync with back-compat changes (Jason Ginchereau) #12674
Spanish:
972bfe1514 - n-api: Sincronizar con cambios de compatibilidad retroactiva (Jason Ginchereau) #12674
To enable N-API support for node versions back to v4, the N-API code can also be built as an external addon. To make maintenance easier, a single codebase needs to support both built-in and external scenarios, along with Node versions >= 4 (and corresponding V8 versions).
This change includes several minor fixes to avoid using node internal APIs and support older V8 versions.
English:
f204945495 - deps: add example of comparing OpenSSL changes (Daniel Bevenius) #13234
Spanish:
f204945495 - deps: añadir ejemplo de comparación de cambios de OpenSSL (Daniel Bevenius) #13234
When upgrading OpenSSL, Step 6 in upgrading guide explains the steps that need to be taken if asm files need updating. This might not always be the case and something that needs to be checked from release to release.
This commit adds an example of using github to manually compare two tags to see if any changes were made to asm files.
English:
98e54b0bd4 - meta: restore original copyright header (James M Snell) #10155
Spanish:
98e54b0bd4 - meta: restaurar la cabecera de copyright original (James M Snell) #10155
A prior io.js era commit inappropriately removed the original copyright statements from the source. This
restores those in any files still remaining from that edit.
Languages
This contribution was translated from English to Spanish.
Word Count
- In this contribution, I've translated 1117 words
- I've translated a total of 45521 words so far.
Previous translations on this project
- Part 37
- Part 36
- 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.
Greetings, @cremisi. Thanks for submitting your contribution!
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
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!