[Translation][Spanish] Node.js, from English (1,070 words) [N'35]

Image source

Github Repository

https://github.com/nodejs/i18n

Project Details

By definition, Node.js is a Java Runtime Environment (JRE). But it is more than just that. While common JREs function as machine backups that allow users to smoothly run JavaScript on their browsers and applications, this open-source project functions as an app that manages Java code by itself. It's practical uses for developers are endless. It grants an extraordinarily versatile platform for designing code, programs, websites and other applications. And that isn't all: Node provides a virtual facility for testing the proper work of Java-driven programs and devices –and their planned updates–, helping to find bugs, solve errors, fix code and vastly improving their performance.

I believe all the amazing uses of Node are to be considered by themselves and I declare myself a fan of the project. But, besides, I support it for its functionality as a medium for bringing to reality countless creations that can be as good as Node itself. If you can dream it –and code it in JavaScript–, then your imagination is the only limit!The open translation of Node to thirty-three (33) languages proves the advantages of open-source projects when it comes to diversification of knowledge and worldwide spreading of useful tools.

Ahead, there is the link of the program's webpage:

https://nodejs.org

Contribution Specifications

Translation Overview

This is my 35th contribution to Node.js as a translator. For this collaboration, I continued my previous work, on the repl.md file of Node.js' version 6, which, as its name indicates, contains the documentation of the REPL's implementation within the program.

In my last report, I briefly explained the consistence of REPL and its main uses for programs like Node.js. Here, I'll refer here an extract of said report:

"This acronym stands for Read-Eval-Print-Loop. It is a simplistic, but very versatile, interactive programming environment. In it, users input information to a program through a console, this one reads it, evaluates it and returns determined expected results. REPL is specially useful for JavaScript, since is one of the command-line-alike programs that support the usage of scripts..."

Image source

Now, let's dig a little deeper into the way these implementations work.

As their name suggest, REPLs are made by the continuous execution within a program of three basic functions: 1) Read; 2) Evaluate; 3) Print. Let's check on that step by step.

1. Read

During the reading phase of the REPL, the program accepts an expression inputted by the user through a console (I explained the way consoles work in previous contributions, analyses it and checks for coincidences with a list of acceptable writings in its database. If there are matching values within this list, then it takes them as valid entries and the loop proceeds to its next phase.

GIF source

2. Evaluate

The second phase of the loop consists in the evaluation of the entered expressions. Once an entry is considered valid, the program takes its contents and determines which operation is needed to be performed and which are the arguments and values to include in said operation.

GIF source

3. Print

The third and last phase of the loop is also the simplest of them all. In it, the program shows the results of the operations that took place during the evaluation step. If results are too complex to be human-readable, then the console turns it into something that is easier to understand –according to a predefined set of rules and procedures to be applied– and, then, emits them on the console.

GIF source

Besides this explanation, I would like to add a couple of considerations on these matters that could come quite useful for you. The translated file specifies that the evaluation phase of the REPL is performed by a predefined evaluator that just accepts the following expressions as input:

BUT!... If you have thought about an usage for your REPL that requires a different evaluation function, you can specify a personally crafted one that suits your necessities. The only condition the Node's development team has for you on this issue is that you introduce it when you create a new REPL server... Or, as specified by the manual here, a new:

repl.REPLServer

You can check more about the aforementioned concepts here:

• https://stackoverflow.com/questions/13603021/what-is-a-repl-in-javascript
• https://www.computerhope.com/jargon/r/repl.htm
• https://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop
• https://softwareengineering.stackexchange.com/questions/168285/difference-between-a-repl-and-interactive-shell
• https://www.geeksforgeeks.org/javascript-eval-function/
• https://www.w3schools.com/jsref/jsref_eval.asp
• http://lib.ru/JAVA/javascr/expr.html
• https://dev.to/promhize/javascript-in-depth-all-you-need-to-know-about-expressions-statements-and-expression-statements-5k2

Expect more information and tips on the next report!

Image source

• Work example #01:

English:

The following illustrates a hypothetical example of a REPL that performs translation of text from one language to another:

Spanish:

Lo siguiente ilustra un ejemplo hipotético de un REPL que traduce texto de un idioma a otro:

• Work example #02:

English:

As a user is typing input into the REPL prompt, pressing the <0> key will
send the current line of input to the <1>eval</1> function.

Spanish:

Cuando un usuario esté ingresando una entrada en el campo de texto del REPL, presionar la tecla <0> enviará la línea actual del input a la función <1>eval</1>.

• Work example #03:

English:

The <0>useColors</0> boolean option can be specified at construction to instruct the default writer to use ANSI style codes to colorize the output from the <0>util.inspect()</0> method.

Spanish:

La opción booleana <0>useColors</0> puede especificarse en la construcción, para ordenarle al escritor predeterminado que utilice códigos de estilo ANSI para dar color al output del método <0>util.inspect()</0>.

Languages

This translation was made from English to Spanish.

I got plenty experience translating and proofreading this project as an Utopian contributor. I collaborate here as translator and Language Moderator of the Da-Vinci/Utopian Spanish translation team. Besides this project, I have experience translating and proofreading The Curious Expedition, Ancap-ch, Byteball Wiki, OroCrm and BiglyBT.

Word Count

• The amount of words translated in this contribution is: 1,070.

Note: This number is the result of subtracting the complete sum of non-translatable content to the word-count Crowdin has done for the period in which this contribution was done.

• The total amount of words translated in this project (as a Da-vinci/Utopian translator) is: 43,725.

Previous Translations of the Project

• Contribution N'01. Submitted on September 13th, 2018.
• Contribution N'02. Submitted on September 15th, 2018.
• Contribution N'03. Submitted on September 17th, 2018.
• Contribution N'04. Submitted on September 19th, 2018.
• Contribution N'05. Submitted on September 21th, 2018.
• Contribution N'06. Submitted on September 22th, 2018.
• Contribution N'07. Submitted on September 23th, 2018.
• Contribution N'08. Submitted on October 1st, 2018.
• Contribution N'09. Submitted on October 8th, 2018.
• Contribution N'10. Submitted on October 14th, 2018.
• Contribution N'11. Submitted on October 15th, 2018.
• Contribution N'12. Submitted on October 18th, 2018.
• Contribution N'13. Submitted on October 21st, 2018.
• Contribution N'14. Submitted on October 24th, 2018.
• Contribution N'15. Submitted on October 27th, 2018.
• Contribution N'16. Submitted on October 31th, 2018.
• Contribution N'17. Submitted on November 3rd, 2018.
• Contribution N'18. Submitted on November 4th, 2018.
• Contribution N'19. Submitted on November 6th, 2018.
• Contribution N'20. Submitted on November 17th, 2018.
• Contribution N'21. Submitted on November 24th, 2018.
• Contribution N'22. Submitted on December 7th, 2018.
• Contribution N'23. Submitted on December 15th, 2018.
• Contribution N'24. Submitted on December 20th, 2018.
• Contribution N'25. Submitted on December 26th, 2018.
• Contribution N'26. Submitted on December 28th, 2018.
• Contribution N'27. Submitted on December 30th, 2018.
• Contribution N'28. Submitted on January 9th, 2019.
• Contribution N'29. Submitted on January 10th, 2019.
• Contribution N'30. Submitted on January 12th, 2019.
• Contribution N'31. Submitted on January 18th, 2019.
• Contribution N'32. Submitted on January 19th, 2019.
• Contribution N'33. Submitted on January 24th, 2019.
  *Contribution N'34. Submitted on January 28th, 2019.

Proof of Authorship

This translation was made during January 29th. You can check the translation record in my Crowdin account [here], the activity on the project's Crowdin [here] and a summary of recent additions to the project [here].