[Translation][Spanish] Node.js (1204 words) (Part 68)

Source

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

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.

^Source

Contribution Specifications

• Translation Overview

This is my 68# contribution to Node.js. The translation of the project is advancing nicely, at this moment, the Spanish team has translated 69% of the entire project. In my case, for this contribution I translated instructions that were written by developers with the goal of improving the performance of the software.

One of the best aspects of Node.js, is that besides its great versatility which makes it a very useful tool for developing digital platforms, is the fact that this software is completely open source, which means any person from anywhere on the world can have free access to Noje.js’s source code.

This makes it easier to identify bugs and errors, and at the same time, it allows the community to join forces and figure out solutions that can be implemented to constantly improve Node.js’s features. The platform that is used to handle all of this collaboration with the global community of developers is GitHub. In there, developers can find all of the information they need, and they can also propose changes or instructions to fix issues that could affect the performance of the software.

The content I translated consisted mostly in instructions that were originally posted in GitHub by developers and they are always written following the same template, which is the following:

• Github link to the original commit
• The area related to the instruction or change, such as “test”, “doc”, “fs” among many others.
• The instruction itself, always with imperative verbs and sometimes using abbreviations and technical terms.
• The name or username of the developer that proposed this.
• The final GitHub link to the merged pull request.

Below we can see a few examples of the instructions I translated.

English

remove duplicate export

Spanish

remover exportación duplicada

There was a previous change where module.exports started using a more efficient pattern, but there was a mistake in the implementation of the change because the developer “left a duplicate export around for OutgoingMessage.” ^Source Luckily, another developer realized this mistake and fixed it.

---

English

improve documentation.md

Spanish

mejorar documentation.md

Given the fact Node.js is a very complex software with a variety of uses and popularity, it has a lot of documentation that is meant to facilitate things for developers. This documentation can be improved as time goes on and the software is updated. In this case, a developer decided it was a good idea to reword some parts of the documentation and do other little modifications to improve the quality.

^Source

---

English

edit CONTRIBUTING.md preamble

Spanish

editar el preámbulo de CONTRIBUTING.md

In this case, a developer decided he could improve the quality of the writing of the preamble, and decided to do it. He informed the community about this change, and it was eventually accepted and implemented. Specifically, he made it “more concise and focused.” ^Source

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, primitives, and CVE.

---

• 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

The word count of this contribution is the number of words translated after subtracting words that aren’t changed, such as names, links, functions.

Part 68: 1204 words

The total numbers of words includes every word in the final translated strings, including those that aren’t actually translated, such as names, links, functions.

Total:

Proof of Authorship

My activity on Crowdin