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

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 44th contribution to Node.js as a translator. For this collaboration, I continued my previous work on Node.js’ version 6 url.md file, which describes the features, characteristics and uses of url module of Node, translated the querystring.md file of the same version, explaining the the specifications of the querystring module, and continued the translation (begun by another member of the Da-Vinci Spanish translation team) of the punycode.md file, also from that version, discussing the punycode module.

In my previous contributions, i talked about URLs and expatiated on its Node.js' module functioning:

URL stands for Uniform Resource Locator and is the text references to web addresses. What this module does is resolving and parsing these. For this, the module counts with two APIs: a legacy API and an API that implements the WHATWG URL Standard used by web browsers.

Image source

For this collaboration, I'll explain what is a querystring, as I translated a file with that name and said concept is addressed on many sections of the Node.js' documents I've been working on. A querystring is a set of characters that are to be input in a search platform on a net browser, computer or other digital data-storing device to receive information from it. Its composition varies depending upon the operating system specifications.

GIF source

Finally, as I finished the translation on the Punycode document, I’ll explain what is it. Punycode is an encoding mechanism that relies on Unicode to simplify data content and make it readable on web browsers. On an important note, the module that regulates and controls the usage of querystring in Node is a third party tool that the developers of the program thought useful to incorporate to its main system. Modifications to the module are to be adressed to the independent project, and not to Node. Its webpage is:

https://mths.be/punycode

Image source

You can find out more about the aforementioned concepts here:

• https://www.techopedia.com/definition/1352/uniform-resource-locator-url
• https://searchnetworking.techtarget.com/definition/URL
• https://en.wikipedia.org/wiki/URL
• https://whatis.techtarget.com/definition/querystring
• https://www.techopedia.com/definition/1228/query-string
• https://www.w3schools.com/asp/coll_querystring.asp
• https://www.webopedia.com/TERM/P/Punycode.html
• https://punycode.io/
• https://en.wikipedia.org/wiki/Punycode

Image source

Thanks for taking your time to read! Expect more information and tips on the next report :)

Image source

• Work example #01:

English:

The C0 control percent-encode set is used for all other cases, including URL fragments in particular, but also host and path under certain specific conditions.

Spanish:

El conjunto de codificación porcentual de control C0 es utilizado para todos los otros casos, incluyendo fragmentos de URL en particular, pero también host y ruta bajo ciertas condiciones específicas.

• Work example #02:

English:

It is exported primarily to allow application code to provide a replacement percent-encoding implementation if necessary by assigning querystring.escape to an alternative function.

Spanish:

Principalmente, se exporta para permitir que el código de aplicación proporcione una codificación porcentual de remplazo, de ser necesario, asignando querystring.escape a una función alternativa.

• Work example #03:

English:

Because host names in URLs are limited to ASCII characters only, Domain Names that contain non-ASCII characters must be converted into ASCII using the Punycode scheme.

Spanish:

Ya que los nombres de hosts en los URLs se limitan a caracteres ASCII únicamente, los Nombres de Dominio que contengan caracteres no ASCII deberán ser convertidos a ASCII utilizando el esquema de Punycode.

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,205.

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: 54,656.

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.
• Contribution N’35. Submitted on January 31st, 2019.
• Contribution N’36. Submitted on March 3rd, 2019.
• Contribution N’37. Submitted on March 6th, 2019.
• Contribution N’38. Submitted on April 3rd, 2019.
• Contribution N’39. Submitted on April 16th, 2019.
• Contribution N’40. Submitted on April 19th, 2019.
• Contribution N’41. Submitted on May 28th, 2019.
• Contribution N’42. Submitted on July 8th, 2019.
• Contribution N’43. Submitted on July 13th, 2019.

Proof of Authorship

This translation was made between July 16th and July 30th, 2019. 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].