Repository
https://github.com/nodejs/i18n
Project Details
Node.js, by definition, is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code outside the browser. This means that now it is possible to execute a program written in JS outside a web browser such as Google Chrome, Safari, etc. This creates an extension to what the language can do, besides just creating interactive websites. With the help of the V8 JavaScript runtime engine, it can now take the code and convert it into a faster machine code, e. g., Node.js eliminates the waiting and continues to take care of the next task.
From my personal perspective, Node.js represents an advantage for the coders to write code, since it still has all the capabilities and functionalities JavaScript offers, but now in a more extended way. Also, thanks to all the time I have been contributing with this project, I have realized the huge amount of time and effort that the Node.js team has taken in order to make it as good as it is and also to improve it with every single upgrade.
You can take a look at their Crowdin project here.
Contribution Specifications
- Translation Overview
This is the 46th translation I made for the Node.js project, and on this contribution I finished translating the WRITING-AND-RUNNING-BENCHMARKS.MD and the WRITING-TESTS.MD folders, and I started with MANTAINING-V8.MD. As I already defined the first two in my previous posts, I am just going to define the last one:
-- MANTAINING-V8.MD: The intention of this folder is to inform the coders the right way to maintain the V8 engine. It starts by showing its background, the requirements for the support and the maintaining process. This is a very important folder since it informs the user about the different fixed and unfixed bugs on it, how to get rid of them and the way to do a backport.
Since on this folder you can't find the definition what V8 exactly is, I would like to share it, because I believe it is essential to understand the context as a whole.
Chrome V8, or also known as just V8, is an open-source JS engine developed by the Chromium Project for Google Chrome and Chromium web browsers. Its function is to compile JavaScript directly to native machine code before executing it, instead of more traditional techniques, such as interpreting bytecode or compiling the program to machine code. The code that has been compiled is later additionally optimized (an re-optimized) dynamically at runtime.
Now, let's talk about a new term I found on this contribution: Backport.
Backporting is defined as the action of taking different parts from a newer version of a computer software or a software component and later porting them to an older version of the same program or software. This is a part of the maintenance step in a software development process, and it is usually used for fixing security issues in older versions of the software, and it works also for providing new features to older versions.
I would like to clarify that these words, both backport and backporting were kept untranslated since they are both used that way in Spanish as well.
Examples of strings translated:
1. EN: Maintaining V8 in Node.js
SP: Mantenimiento de V8 en Node.js
2. EN: V8 Release Schedule
SP: Programa de Lanzamiento de V8
3. EN: V8 only supports active branches.
SP: V8 sólo soporta ramas activas.
References:
-- Wikipedia. Chrome V8 (https://en.wikipedia.org/wiki/Chrome_V8)
-- Wikipedia. Backporting (https://en.wikipedia.org/wiki/Backporting)
- Languages
I translated from English to Spanish.
I have translated over 100,000 words utilizing the Crowdin platform and this has given me experience to always grant great quality translations.
- Word Count
I have translated 1,061 words. This contribution has been made between the dates Feb/4/2019, when I realized the translation, and Feb/6/2019, when I realized the corrections.
Previous translations on this project:
- Part 1
- Part 2
- Part 3
- Part 4
- Part 5
- Part 6
- Part 7
- Part 8
- Part 9
- Part 10
- Part 11
- Part 12
- Part 13
- Part 14
- Part 15
- Part 16
- Part 17
- Part 18
- Part 19
- Part 20
- Part 21
- Part 22
- Part 23
- Part 24
- Part 25
- Part 26
- Part 27
- Part 28
- Part 29
- Part 30
- Part 31
- Part 32
- Part 33
- Part 34
- Part 35
- Part 36
- Part 37
- Part 38
- Part 39
- Part 40
- Part 41
- Part 42
- Part 43
- Part 44
- Part 45
Proof of Authorship
Word Count
