Since Node.js is very easy to learn and it provides a lot of benefits for developers, there is a huge community of people involved with it, which is one of the reasons why this project is available to be translated into several languages (in crowdin, one of the best translation platforms in the web, this project is available to be translated into 33 different languages, Spanish is the one corresponding to this contribution), the ultimate goal of translating Node.js is to make it easier for developers from any country to start learning about this project in their own native language.
If you want to know more about Node.js feel free to visit its website.
- Translation Overview
This is my 69# contribution to Node.js. The content I have been translating belongs to Node.js’s changelogs and the information we can find here is related to previous changes that were applied to Node.js in order to improve its performance, its documentation, its features, among other useful aspects.
All this information is originally written by developers from the global open source community that collaborate with the development of Node.js. This is one of the most positive aspects of having open source software, anyone can collaborate with the code and help in finding solutions to any bug or issue that could be affecting the software.
The platform that is used to manage the collaborations of all the developers is called GitHub, and it is through this platform that anyone can have access to the code and the last updates of Node.js. All of the changes are submitted using this platform, and once they are implemented the community is informed using this platform as well. Eventually, when it is time to request translations for other languages, it is the Crowdin platform the one that we use. So in short words, the information is first posted by the development community on GitHub, and later on, it is uploaded to Crowdin to facilitate the translations.
Below we can see a few examples of the instructions I translated.
fix compiler warning
corregir la advertencia del compilador
A developer realized there was a little mistake in a compiler warning, and this mistake could cause some confusions or misinterpretations. Therefore, it was decided that a fix should be implemented as soon as possible to prevent any potential problem.
añadir función de emitExperimentalWarning
This instruction consisted in adding a new warning that informed the user if he was using an experimental feature and that it could change at any time given the fact it is experimental. This way the users will be properly informed when using this type of feature.
fix typos in N-API
corregir errores tipográficos en N-API
It is completely understandable to have a few typos when doing some writing, if the person doesn’t double check the writing it could very well have more than one typo. In this case, a developer realized there were some typos in N-API and he submitted his own correction to fix this mistake.
Source language: English
Translated language: Spanish
I have made several contributions in the past, and I published a series of articles in both languages. I am also part of the Utopian + DaVinci Spanish team.
- Word Count
The word count of this contribution is the number of words translated after subtracting words that aren’t changed, such as names, links, functions.
Part 69: 1212 words
The total numbers of words includes every word in the final translated strings, including those that aren’t actually translated, such as names, links, functions.