Github Repository
https://github.com/nodejs/i18n
Project Details
By definition, Node.js is a Java Runtime Environment (JRE). But it is more than just that. While common JREs function as machine backups that allow users to smoothly run JavaScript on their browsers and applications, this open-source project functions as an app that manages Java code by itself. It's practical uses for developers are endless. It grants an extraordinarily versatile platform for designing code, programs, websites and other applications. And that isn't all: Node provides a virtual facility for testing the proper work of Java-driven programs and devices –and their planned updates–, helping to find bugs, solve errors, fix code and vastly improving their performance.
I believe all the amazing uses of Node are to be considered by themselves and I declare myself a fan of the project. But, besides, I support it for its functionality as a medium for bringing to reality countless creations that can be as good as Node itself. If you can dream it –and code it in JavaScript–, then your imagination is the only limit!The open translation of Node to thirty-three (33) languages proves the advantages of open-source projects when it comes to diversification of knowledge and worldwide spreading of useful tools.
Ahead, there is the link of the program's webpage:
Contribution Specifications
Translation Overview
This is my 25th contribution to Node.js as a translator. For this collaboration, I continued my previous work on the CHANGELOG_IOJS.md file, which –as its name indicates– contains the changelog of the io.js’ version of Node.
As I explained in my past translation reports, a changelog is a registry of all the changes made on determined project for each one of its versions. The files created for such purpose list modifications on internal components, substitutions of protocols, updates, deprecations, addition of supported tools, new functions, corrected errors and fixed bugs. In summary: every feature that first appeared or was removed in the program version being addressed must be specified and described in this registry. This is made with the purpose of providing a timeline of the development of the project and, by doing so, helping programmers to check any details they need to understand the way it came to be what it is and improve it in the future.
I'll refer to two of the logs I translated to illustrate the dynamics of the changelog. Both of them are included in the "Commits" section of the addressed file's stable version 2.3.2. The first one goes:
There is one important concept involved in this log. Before we can understand the commit, we need to address this term by itself. I'm about to explain what a "linter" is.
A linter is one of the most helpful programming tools available for the use of developers. Basically, it is a scanner that parses a whole coding material and searches for errors, inconsistencies, and confusing statements within it. It goes further than what compilers do with their basic syntactic parsing, since it considers the logic of values, the results of operations, the placement of the sections inside the code, along some others possible flaws. It was firstly developed as a C-specific tool, but became generally widespread and nowadays most coding languages have their own.
If a linter had a face, it would probably look like this when examining the code of your program:
Knowing these facts, we understand that, since this update, the parsing of Node.js' linter will be different when dealing with commas, solving a previous misunderstanding of the code.
The next log I'll refer is this one:
What we need to understand here is what a "typo" is. As it is defined by the Oxford dictionary, a typo is a typographical error, which means an error in the production on printed –digital printing included here– material, i.e., an error in the technical writing of a sentence that does not reflect the text that was supposed to be written.
Typos can mislead to the misunderstanding of information, as illustrated in the following meme:
And that, kids, is why you need to lookout for typos in whatever you write...
That being said, we can understand the importance of this log. Fixing a typo can prevent a whole piece of text to be wrongly interpreted, which is should be specially avoided in a technical manual like the one is being translated here.
You can check some references here for more information about the previously addressed concepts:
- https://stackoverflow.com/questions/8503559/what-is-linting
- https://nyctomachia.wordpress.com/2016/06/11/what-is-a-linter/
- https://en.wikipedia.org/wiki/Lint_(software)
- https://www.merriam-webster.com/dictionary/typography
- https://en.wikipedia.org/wiki/Typography
All changes included in each one of the versions of the project are formatted as pull-request commits. Id est, they are presented as very brief comments about the action that was suggested, are normally written with imperative verbs, and have a strict limitation on their number of characters (so even complex ideas are reduced to a small amount of words). These specifications made the translation of this document a challenge. However, it was satisfactorily achieved. As you will see in the examples below, the name of the developer who provided each log is often referred inside parenthesis at the end of it.
Work example #01:
English:
[<0>ca93f7f2e6</0>] - <1>deps</1>: upgrade openssl sources to 1.0.2d (Shigeki Ohtsu) <2>#2141</2>
Spanish:
[<0>ca93f7f2e6</0>] - <1>deps</1>: actualizar fuentes de openssl a 1.0.2d (Shigeki Ohtsu) <2>#2141</2>
Work example #02:
English:
[<0>2ba1740ba1</0>] - <1>test</1>: add missing crypto checks (Johan Bergström) <2>#2129</2>
Spanish:
[<0>2ba1740ba1</0>] - <1>test</1>: añadir revisiones criptográficas faltantes (Johan Bergström) <2>#2129</2>
Work example #03:
English:
<0>process.send()</0> is not synchronous as the docs suggest, a regression introduced in 1.0.2, see <1>#760</1>.
Spanish:
<0>process.send()</0> no es sincrónica, como sugieren los docs, una regresión introducida en 1.0.2, vea <1>#760</1>.
Languages
This translation was made from English to Spanish.
I got plenty experience translating and proofreading this project as an Utopian contributor. I collaborate here as translator and Language Moderator of the Da-Vinci/Utopian Spanish translation team. Besides this project, I have experience translating and proofreading The Curious Expedition, Ancap-ch, Byteball Wiki, OroCrm and BiglyBT.
Word Count
- The amount of words translated in this contribution is: 1,789.
- The total amount of words translated in this project (as a Da-vinci/Utopian translator) is: 29,019.
Previous Translations of the Project
- Contribution N'01. Submitted on September 13th, 2018.
- Contribution N'02. Submitted on September 15th, 2018.
- Contribution N'03. Submitted on September 17th, 2018.
- Contribution N'04. Submitted on September 19th, 2018.
- Contribution N'05. Submitted on September 21th, 2018.
- Contribution N'06. Submitted on September 22th, 2018.
- Contribution N'07. Submitted on September 23th, 2018.
- Contribution N'08. Submitted on October 1st, 2018.
- Contribution N'09. Submitted on October 8th, 2018.
- Contribution N'10. Submitted on October 14th, 2018.
- Contribution N'11. Submitted on October 15th, 2018.
- Contribution N'12. Submitted on October 18th, 2018.
- Contribution N'13. Submitted on October 21st, 2018.
- Contribution N'14. Submitted on October 24th, 2018.
- Contribution N'15. Submitted on October 27th, 2018.
- Contribution N'16. Submitted on October 31th, 2018.
- Contribution N'17. Submitted on November 3rd, 2018.
- Contribution N'18. Submitted on November 4th, 2018.
- Contribution N'19. Submitted on November 6th, 2018.
- Contribution N'20. Submitted on November 17th, 2018.
- Contribution N'21. Submitted on November 24th, 2018.
- Contribution N'22. Submitted on December 7th, 2018.
- Contribution N'23. Submitted on December 15th, 2018.
- Contribution N'24. Submitted on December 20th, 2018.
Proof of Authorship
This translation was made December 21st. You can check the translation record in my Crowdin account [here], the activity on the project's Crowdin [here] and a summary of recent additions to the project [here].
a