https://steemitimages.com/0x0/https://ipfs.busy.org/ipfs/QmPNPiKtoRvonftEKcPhP9gHG9ZW6z4MqWSDFF4oHe8ULc

This post is another report of my last Node.js translation of the 9th version of change log folder. In my last report I talked about the importance of this kind of file; now it is time to discuss their structure because it looks really different from any other record file and could be confusing at first.

Each certain time a new version is released and each version has it own changes; this changes are also called "commits". The title of a version has the date of release, the version number and the name of the collaborator that made it. For example

https://ipfs.busy.org/ipfs/QmYSPVqx2448o6yN5ZZUuXevPAHF7gzBWn9eK9WZUUNhRE

Next, there is a brief section of the most notable changes made in that version. In this section the author specifies the changed module, the commit, the author's name and the commit number

https://ipfs.busy.org/ipfs/QmaniffU3ER4KBdgBnNfzzYdRkujrBUgvwGZu6yq3PzVhg

Finally, there is a list with all the commits presented in the version released. These commits have the same format as those in the previous section.

https://ipfs.busy.org/ipfs/QmRhKCV3EWvzerWvggJjWumXvQKgv9gVHNAqvgun2rUeqM

As you can see, there are no complications in a change log file structure. Nontheless, the commits spelling is written in infinitive; this can make the reading very extrange.

### Repository https://github.com/nodejs/i18n ### Project Details > Node.js is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code outside of a browser. It lets developers use JavaScript to write Command Line tools and for server-side scripting to produce dynamic web page content before the page is sent to the user's web browser. Consequently, Node.js represents a "JavaScript everywhere" paradigm,[6] unifying web application development around a single programming language, rather than different languages for server side and client side scripts. [Node.js](https://en.wikipedia.org/wiki/Node.js)

In summary, Node.js is a way to unify a lot of languages in one single code, so there are no support issues between them. A simple solution for a big problem.

I decided to translate this project because I'm an engineering student and programming covers a huge area of knowledge on my career. Also, I like sharing information and a way to do it is translating the content of a big project like this so people around the world can access to it and share it too.

### Contribution Specifications - Translation Overview

In this part of the 9th version of Node.js change log file some new tools have been added. These tools make easier and more efficient a Node.js programm built in process. They also fix some code sections of the source code. The changes made make Node.js more solid and stable, so the users can have a better experience using it.

Some examples of these changes are below:

https://ipfs.busy.org/ipfs/QmNzagrRQn48QvSCQM4PRa1YmsCdf8VXjg1nSm6uUeJbPH

- Languages

The original language of this change log is English and it was translated into Spanish, which is my native language. I have experience translating in projects like Loopring wallet and Yapbam. These projects make me grow and learn a lot about open source projects.

Some examples of my translation:

> ##### English >[<0>077bcbd202] - <1>src: introduce internal buffer slice constructor (Anna Henningsen) <2>#18030 > ##### Spanish >[<0>077bcbd202] - <1>src: introducir constructor interno de porción del buffer (Anna Henningsen) <2>#18030 ________________________________________ > ##### English >[<0>ac0a0a6775] - <1>src: harden JSStream callbacks (Anna Henningsen) <2>#18028 > ##### Spanish >[<0>ac0a0a6775] - <1>src: fortalecer callbacks de JSStream (Anna Henningsen) <2>#18028 ________________________________________ > ##### English >[<0>c4abdcdc30] - <1>(SEMVER-MINOR) <1>stream: avoid writeAfterEnd() while ending (陈刚) <2>#18170 > ##### Spanish >[<0>c4abdcdc30] - <1>(SEMVER-MINOR) <1>stream: evitar writeAfterEnd() al finalizar (陈刚) <2>#18170 ________________________________________ > ##### English >[<0>5b5f5b1b32] - <1>test: add assertions for TextEncoder/Decoder (Sho Miyamoto) <2>#18132 > ##### Spanish >[<0>5b5f5b1b32] - <1>test: agregar aserciones para TextEncoder/Decoder (Sho Miyamoto) <2>#18132 ________________________________________ - Word Count

This constribution consist of 1106 words

![image.png](https://ipfs.busy.org/ipfs/Qma4kKdnW5atp93S2d3ngXpvSfHvpuCbUAVHZBYeJuEE5s) ### Learned Concept

This contribution introduce me a new concept about programming, the 'dead code'. The dead code is "a section in the source code of a program which is executed but whose result is never used in any other computation. The execution of dead code wastes computation time and memory.". It is a very important concept because as it looks unnecessary, its elimination can produce a malfunctioning in the program,so the collaborators and developers must be very careful when making changes in these specific parts.

My interest in this concept is because in one commit there is a dead code elimination and I thought that was code that doesn´t work and only causes memory usage. In my research I realized that my thought wasn't correct.

[Dead Code](https://en.wikipedia.org/wiki/Dead_code) ### Proof of Authorship

You can visit my profile (navx) on Crowdin's website to find proof of authorship. Also, you can visit the Activity tab in the Node.js project and filter my contributions between October 27th and October 29th, which were the dates of the translation and the corrections respectively.

[Activity Tab](https://crowdin.com/project/nodejs/activity_stream) The next link, redirect to my crowdin profile: https://crowdin.com/profile/navx ____________________________________ ## Best Regards!