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 #49 contribution to Node.js, on this occasion all of the strings I translated were from the commits section.
This type of string is always very similar because they always consist in brief instructions regarding changes that must be applied with the goal of improving the way Node.js is currently working.
The people who propose these changes are developers or other technical users that discover bugs or issues, and by using the GitHub platform, they are able to share with other developers the information about their findings, and propose what they think can be a good solution.
Since every person handling this information has some technical knowledge, it is very common to see some strings making references to other internal elements of the software, or simply using technical terms that aren’t very well know by the general public.
This means when a person is translating these strings, it is highly recommended to take the time and do some research on the technical terms in case there are doubts regarding the meaning of those words.
Below I added some examples of the strings I translated for this contribution:
add check for large strings
añadir chequeo para strings grandes
This change was proposed because v8 only works with strings that can fit in an int, and sometimes, node.js’s n-api would specify a larger size, so to prevent any confusion and potential bugs in the future, a check was added to make sure the strings have the proper size.
stop creating references to primitives
dejar de crear referencias a primitivos
A test was creating unnecessary references to primitives, the point of this test was to make sure “the finalize callback gets called when it should get called, that it gets called with the correct pointer, and that it does not get called when it should not get called. Creating persistent references is not necessary for verifying this.” Source To fix this little issue, a change was proposed, and eventually, applied.
add coverage for napi_typeof
añadir cobertura para napi_typeof
There wasn’t a specific test that could evaluate napi_typeof in its entirely, therefore, a proposal was made to add a new test that could make sure everything was compatible and able to work without any issue.
When working on this contribution I was able to learn the following concept:
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
Part 49: 1012 words
Total: 54362 words