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 50# contribution to Node.js, and since I am translating changelogs, it is not a surprise that the majority of the strings are short instructions that provide a brief explanation of an individual change that should be applied with the goal of improving the way Node.js is currently working.
These changes aren’t only related to the modification of internal elements of the software (like modules and add-ons, among many others), but they are also related to the improvement of the documentation that helps people make the best use out of this software, this is why a considerable proportion of the listed changes are about making modification to relevant text, and important documents, so the information available in them is as accurate as possible.
However, regardless of the nature of the change, each of these strings is always written using the same template, which includes the following information:
- Link to the commit from GitHub
- Area related to the change
- The change itself, written in a very concise way, often using abbreviations and technical terms.
- The name of the person who proposed the change
- The link to the pull request fromGitHub.
There are some exception where it is also indicated if the change is semver-major or minor, but the great majority of the strings use that structure.
Below I added some examples of the strings I translated for this contribution:
better support for IPv6 addresses
mejor soporte para direcciones de IPv6
This change was proposed, because there were a few issues regarding the management of Ipv6 addresses when setting the servername in the host header, besides, there were also some issues about the format used when comparing IP addresses in the subjectAltName field of a certificate. Source
be less tentative about undefined behavior
ser menos tentativo sobre comportamientos indefinidos
This change is simply about the writing style used in a document, particularly in the documentation of the buffer module, the modification in question consisted in changing "the result is considered undefined behavior" to "the resulting behavior is undefined" because that way it would be “less ambiguous in meaning and less awkward stylistically”. Source
upgrade openssl sources to 1.0.2o
actualizar fuentes de openssl a 1.0.2o
Since Node.js is a software that’s constantly being updated and improved, sometimes it is necessary to apply changes to internal elements to make sure everything is running as smooth as possible, in this case, the change consisted in updating the openssl sources.
When working on this contribution I was able to learn the following concepts:
CVE: when doing this translation I noticed this acronym was used in several strings, so I decided to do a little bit of research and it turns out that CVE means Common Vulnerabilities and Exposures, this is a system that provides help when it comes to handling well-known vulnerabilities in the cybersecurity scene. Source
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 50: 1028 words
Total: 55390 words