Repository:
https://github.com/nodejs/i18n
Project Details:
Node.js is a Java Runtime Environment that enables developers to execute coding tasks operating with JavaScript within their machines. This open-source project is addressed to developers who want to expand their options and abilities in the execution of Java, being able to use this as a instrument for designing and testing infinite applications and processes. It allows a personal and customizable use, supplying users with all the tools they need to make the most of the great amount of features JavaScript offers.
Node is a valuable open-source project since it gives developers tools to improve their performance by using Node.js environment. It also encourages the constant feedback from the source to the audience; it shows different ways of solving problems and optimizing process which in turn, at the end, helps you to learn new ways of doing the same thing and also in an optimized way.
Contribution Specifications:
Translation Overview:
This contribution gathers three different translations that by their amount of words count as one. They are Punycode.md, Maintaining-npm.md, and Debugger.md (its last part).
The first text, Punycode, describes a third-party dependency module used by Node.js and is made available to developers as a convenience. It talks about a character-encoding scheme defined by RFC 3492 that is primarily intended for use in Internationalized Domain Names. These contain non-ASCII characters that must be converted into ASCII using the Punycode scheme.
Punycoder is operated from Prague by Glueo. As it is stated in Wikipedia: “Punycode, host names containing Unicode characters are transcoded to a subset of ASCII consisting of letters, digits, and hyphen, which is called the Letter-Digit-Hyphen (LDH) subset. For example, München (German name for Munich) is encoded as Mnchen-3ya.”
“The Punycode syntax is a method of encoding strings containing Unicode characters, such as internationalized domain names (IDNA), into the LDH subset of ASCII favored by DNS. It is specified in IETF Request for Comments 3492.”
As stated in RFC 3492, "Punycode is an instance of a more general algorithm called Bootstring, which allows strings composed from a small set of 'basic' code points to uniquely represent any string of code points drawn from a larger set." Punycode defines parameters for the general Bootstring algorithm to match the characteristics of Unicode text. This section demonstrates the procedure for Punycode encoding, using the example of the string "bücher" (Bücher is German for books), which is translated into the label "bcher-kva".
The second text, Maintaining-npm, indicates the process step by step on how clone a npm of Node.js, to upgrade and update it, and to set a new npm from the beginning. It is a very short and concise text that gives simple direction to developers to use this tool of Node.js.
As it is stated in its Website, NPM.js helps to install, share, and distribute code; to manage dependencies in your projects; and, to share & receive feedback with others. It encourages to find Libraries like jQuery, Bootstrap, React, and Angular, and components from frameworks such as Ember. Additionally, it promotes the discovering of packages for mobile, IoT, front end, back end, robotics. It represents a boost for any enterprise since it allows the building of assemble packages like building blocks to quickly develop awesome new projects. Definitely, NPM.js is a very versatile tool that will give developers the upgrade and update necessary to create personalized tools for themselves and their business.
https://www.npmjs.com/
Lastly, the third text is entitled Debugger which is the closing of the previous file I was working on previously. It talks about a depuration process that is included in Node.js as a useful tool that enables the out-of-process debugging utility accessible via a V8 Inspector and a built-in debugging client. This option describes step by step how the developer can do the full process in order to maintain the functions of the program.
As it is indicated in Wikipedia page, “This versatile tool tests and debugs other programs (the "target" program). The code to be examined might alternatively be running on an instruction set simulator (ISS), a technique that allows great power in its ability to halt when specific conditions are encountered, but which will typically be somewhat slower than executing the code directly on the appropriate (or the same) processor. Some debuggers offer two modes of operation, full or partial simulation, to limit this impact.” When the program "traps" or reaches a preset condition, the debugger typically shows the location in the original code if it is a source-level debugger or symbolic debugger, commonly now seen in integrated development environments. If it is a low-level debugger or a machine-language debugger it shows the line in the disassembly (unless it also has online access to the original source code and can display the appropriate section of code from the assembly or compilation).
Despite of the length of these texts and their nature of manuals that describes how to conduct important processes for the right functioning of Node.js, it gives plenty information to look and research for in order to understand the processes that are intended to explain. Examples of this can be seen in some terms such as array, a different function of the ASCII code, the definition of a npm, the concept of debugger and, a new perspective of the use of the word “argument”. Interesting concepts and forms that help to improve in the understating of the work done and extend the word range managed in the project.
As they’re seen in the three texts, the following examples show hints of the nature of the documents:
Example #1:
*English:
The <0>punycode.decode()</0> method converts a <1>Punycode</1> string of ASCII-only characters to the equivalent string of Unicode codepoints.
*Spanish:
El método <0>punycode.decode()</0> convierte una string <1>Punycode</1> de caracteres ASCII únicamente a la string equivalente de puntos de código de Unicode.Example #2:
English:
Note: please run <0>npm dist-tag ls npm</0> and make sure this is the <0>latest</0> <1>dist-tag</1>.Spanish:
Nota: Por favor, corra <0>npm dist-tag is npm</0> y, asegúrese de que es la <0>latest</0> <1>dist-tag</1>.Example #3:
English:
Inserting the statement <0>debugger;</0> into the source code of a script will enable a breakpoint at that position in the code: (…)Spanish:
Insertando la instrucción <0>debugger;</0> en el código fuente de un script habilitará un punto de interrupción en esa posición en el código: (…)
Languages:
This translation was from English to Spanish.
I am a translator in Spanish, English and French. I also work as an English and Spanish teacher as a second or foreign language. I have worked with technical translations in different topics being this one interesting due to the technical terms and use when translating.
Word Count:
Words translated were: 1020.
Total amount words translated in this project: 3520
Pervious Contributions to this Project:
- Contribution n. 1: Domain.md, published on September 19th.
- Contribution n. 2: Debugger.md, published on October 7th.
Proof of Authorship:
Proof of authorship is verifiable by clicking in my Crowdin profile, especially in my contribution by checking my activity, and in the translated texts Punycode, Maintaining-npm, and Debugger.
