<center>![](https://cdn.steemitimages.com/DQmQPWKpofUTSNs5ZZCw7m6etqsLShgShoNAJ6peVvxhgTy/node.png)</center>

<center>[Source](https://en.wikipedia.org/wiki/File:Node.js_logo.svg)</center>

#### 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 allows the creation of Web servers and networking tools using JavaScript and a collection of "modules" that handle various core functionality... Node.js represents a "JavaScript everywhere" paradigm, unifying web application development around a single programming language, rather than different languages for server side and client side scripts. | [Source](https://en.wikipedia.org/wiki/Node.js)

In simple words, this project brings value to the open source community because it facilitates the creation of all sort of applications using JavaScript, and provides a lot of help and versatility to developers, so much so that well-known companies like Netflix, Paypal, and Uber (among many others) use Node for their online services.

Since Node.js is very easy to learn and it provides a lot of benefits for developers, there is a huge community of people involved with it, which is one of the reasons why this project is available to be translated into several languages (in crowdin, one of the best translation platforms in the web, this project is available to be translated into 33 different languages, Spanish is the one corresponding to this contribution), the ultimate goal of translating Node.js is to make it easier for developers from any country to start learning about this project in their own native language. 

 If you want to know more about Node.js feel free to visit its [website.](https://nodejs.org/en/)

#### Contribution Specifications

- Translation Overview

This is my 50# contribution to Node.js, and since I am translating changelogs, it is not a surprise that the majority of the strings are short instructions that provide a brief explanation of an individual change that should be applied with the goal of improving the way Node.js is currently working. 

These changes aren’t only related to the modification of internal elements of the software (like modules and add-ons, among many others), but they are also related to the improvement of the documentation that helps people make the best use out of this software, this is why a considerable proportion of the listed changes are about making modification to relevant text, and important documents, so the information available in them is as accurate as possible. 

However, regardless of the nature of the change, each of these strings is always written using the same template, which includes the following information: 

* Link to the commit from GitHub
* Area related to the change
* The change itself, written in a very concise way, often using abbreviations and technical terms.
* The name of the person who proposed the change
* The link to the pull request fromGitHub.

There are some exception where it is also indicated if the change is semver-major or minor, but the great majority of the strings use that structure. 

Below I added some examples of the strings I translated for this contribution:

English

> better support for IPv6 addresses

Spanish

> mejor soporte para direcciones de IPv6

This change was proposed, because there were a few issues regarding the management of Ipv6 addresses when setting the servername in the host header, besides, there were also some issues about the format used when comparing IP addresses in the subjectAltName field of a certificate. [Source](https://github.com/nodejs/node/commit/8e7ac25aa6)

***

English

> be less tentative about undefined behavior

Spanish

> ser menos tentativo sobre comportamientos indefinidos

This change is simply about the writing style used in a document, particularly in the documentation of the buffer module, the modification in question consisted in changing "the result is considered undefined behavior" to "the resulting behavior is undefined" because that way it would be “less ambiguous in meaning and less awkward stylistically”. [Source](https://github.com/nodejs/node/commit/838f7bdb6e)

***

English 

> upgrade openssl sources to 1.0.2o

Spanish

> actualizar fuentes de openssl a 1.0.2o

Since Node.js is a software that’s constantly being updated and improved, sometimes it is necessary to apply changes to internal elements to make sure everything is running as smooth as possible, in this case, the change consisted in updating the openssl sources.

***

When working on this contribution I was able to learn the following concepts:

**CVE**: when doing this translation I noticed this acronym was used in several strings, so I decided to do a little bit of research and it turns out that CVE means Common Vulnerabilities and Exposures, this is a system that provides help when it comes to handling well-known vulnerabilities in the cybersecurity scene. [Source](https://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures)

In the previous contributions, I included the definition of these terms: deprecation, I/O - input/output, callback, asynchrony, POSIX, parsing, path, wildcard, wrapper function, stack trace, floating point value, error-first callbacks, transpilation tool, root certificate, little-endian,  DNS rebinding,  same-origin-policy, keep-alive behavior, stringification, arrow function, salt (cryptography), semver, lint, fixtures modules, newline, backporting, shell command, ES6 Classes , code refactoring, tarball, benchmark, type-check, deflate, char, aix, spawn, rehash, noop, rebasing, continuous integration, linkify, segfaults, IPC, libuv, toolchain, punycode, symlink, base64, interprocess communication (IPC), application binary interface (ABI), read–Eval–Print Loop (REPL), advanced Interactive eXecutive (AIX), GYP, Opaque binary blob (obb), symbolic link, destructuring, dotfiles, transport layer security (tls), realpath function, watchdog, continuous integration, smoke test, hotfix, data execution prevention,  (DEP), try/catch blocks, off-by-one error, carriage return, ESLint, hard code, hook, Resource Acquisition Is Initialization or RAII, Coverity, nit, backtick, hashes, big endian, nop, redux, shorthand, TPR records, rest parameters, javaScript Object Notation (JSON), N-API, and primitives.

***

- Languages

Source language: English

Translated language: Spanish

I have made several contributions in the past, and I published a series of articles in both languages. I am also part of the Utopian + DaVinci Spanish team.


- Word Count


Part 50: 1028 words

<center>https://cdn.steemitimages.com/DQmTDo7gvTmBpSHk7qwtAt5MursQt8pTYCL3x8ANkpyD1Wn/image.png</center>


Total: 55390 words

<center>https://cdn.steemitimages.com/DQmTewTVNZWSXU6xU5ZaMkAoDwiFqq6cszLDpb1s7KBM4UD/image.png</center>

### Proof of Authorship

[My activity on Crowdin](https://crowdin.com/profile/dedicatedguy/activity)