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 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 53rd translation I have made for the Node.js project, and on this contribution I continued translating the RELEASES.MD folder. Here's a brief description of the last one:
-- RELEASES.MD: This folder describes the release process to follow in relation to its technical aspects. It defines, step by step, all the important details one has to know to release an, for example, update. It goes from who are the individuals that have the power to do so, to the syntax to use once a release is done.
Since I have already described what this folder is about in the last post, I am going to jump straight to the new terms I have found throughout this contribution that needed further information in order to be translated correctly.
The first term I found was Smoke Testing. In computer programming, a smoke testing (also known as confidence testing, sanity testing, build verification test and build acceptance test) is defined as a preliminary test to discover simple failures to reject prospective software release. In other words, it is a software testing that allows you to determine if a deployed build is stable or not. This test helps us to verify whether the important features are working correctly (or not) and that there are no showstoppers in the build that is under testing.
Here is the cycle where smoke testing is involved:
A smoke testing brings a lot of advantages in order to know the functionality of a code before it is released. Here's a brief list of those advantages:
- Easy to perform testing
- Defects will be identified in early stages.
- Improves the quality of the system
- Reduces the risk
- Progress is easier to access.
- Saves test effort and time
- Easy to detect critical errors and correction of errors.
- It runs quickly
- Minimises integration risks
The next term is ccache. At first I thought it was a typing error of "cache", but then I Googled it and I found that it is actually a term, however it is related to it. Ccache is a compiler cache that catches the output of C/C++ compilation, so the next time, the same compilation can be avoided and the results are taken from the cache. Basically it speeds u recompilation by catching previous compilations and detecting when the same compilation is being done once again.
Here's a graph that shows the effect on time using ccache.
Ccache is free software, released under the GNU General Public License version 3 or later.
Examples of strings translated:
1. EN: At the top of each <0>CHANGELOG_*.md</0> file, and in the root <0>CHANGELOG.md</0> file,
there is a table indexing all releases in each major release line.
SP: Por encima de cada archivo <0>CHANGELOG_*.md</0>, y en el archivo <0>CHANGELOG.md</0> raíz, hay una tabla que indexa todos los lanzamientos en cada línea de lanzamiento mayor.
2. EN: A link to
the new release needs to be added to each.
SP: Es necesario
añadir un enlace a cada uno de los nuevos lanzamientos.
3. EN: Step 3: Update any REPLACEME tags in the docs
SP: Paso 3: Actualizar cualquier etiqueta de REPLACEME en los documentos
References:
-- Wikipedia. Smoke Testing (https://en.wikipedia.org/wiki/Smoke_testing_(software))
-- Guru99. What is Smoke Testing? (https://www.guru99.com/smoke-testing.html#6)
-- Wikipedia. ccache (https://en.wikipedia.org/wiki/Ccache)
-- Ccache. (https://ccache.dev/)
- 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,115 words. This contribution has been made between the dates Jun/16/2019, when I realized the translation, and Jun/24/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
- Part 46
- Part 47
- Part 48
- Part 49
- Part 50
- Part 51
- Part 52
Proof of Authorship
Word Count
