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 21st contribution to Node.js as a translator. For this collaboration, I continued my previous work and finished translating the v10’s CHANGELOG_V10.md file!
After doing so, I began translating the v6’s 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 one of the logs I translated to illustrate the dynamics of the changelog. This one belongs to the Semver-patch sub-section of the Commits of v10’s CHANGELOG_V10 file, which, as I said before, I worked in this occasion.
There are two important concepts involved in this log. Being able to understand it requires that we address each of them particularly.
The first one is "deprecation". A deprecation is a voluntary discarding of a specific feature of a software, usually in order to give way to a new –or just better– element to replace it. By deprecating functions, tools and methods to manage situations within Java, the developers of Node.js do not prohibit their use… Just warn the users about how risky and inefficient it would be to utilize them despite the availability of better ways to do what needs to be done. Commonly, when a largely widespread feature is outdated, the programmers give a reasonable time before dispatching it, for users to get its substitute; once that time is over, they deprecate it; and after some more time, they eliminate the compatibility of such component on their platforms (mostly for security concerns).
If you are a visual person… You can imagine a deprecation as a guy dressed as Gandalf stepping in the way of the train you're going in screaming “YOU SHALL NOT PASS”… Of course you can pass… But for one reason or another, it is better if you don’t. He is there for something… Gandalf knows there’s another way to get where you're going.
The second one is “expectWarning”. It is a test to find (and subsequently fix) bugs regarding the warnings that deprecated Node.js’ components shall emit when users try to activate them.
Having explained all that, we can address the quoted entry. With the introduction of that update, the expectWarning test shall include and display the deprecation code of the particular component that is trying to be used. By that, users can now know the specifications of the addressed deprecation and understand why is it better if they choose a different approach to the task they’re trying to complete; this leads to a better documentation by users, and, in that way, an increase in the security of Node (since they should be convinced to use the recommended methods that are suggested by the developers).
You can check some references here for more information about the previously addressed concepts:
- https://www.techopedia.com/definition/24828/deprecated
- https://www.programmerinterview.com/index.php/technical-vocabulary/what-is-deprecated-code/
- https://en.wikipedia.org/wiki/Deprecation
- https://www.javatips.net/api/org.revisionfilter-master/findbugs/src/java/edu/umd/cs/findbugs/annotations/ExpectWarning.java
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>d784dbf36a</0>] - <1>timers</1>: call destroy on interval error (Anatoli Papirovski) <2>#20001</2>
Spanish:
[<0>d784dbf36a</0>] - <1>timers</1>: llamar a "destroy" ante error de intervalo (Anatoli Papirovski) <2>#20001</2>
Work example #02:
English:
[<0>1b05d7bc86</0>] - <1>timers</1>: remove unused variable (Anatoli Papirovski) <2>#18579</2>
Spanish:
[<0>1b05d7bc86</0>] - <1>timers</1>: remover variable no utilizada (Anatoli Papirovski) <2>#18579</2>
Work example #03:
English:
[<0>1bdd3b0dcf</0>] - <1>tools</1>: improve heading type detection in json.js (Vse Mozhet Byt) <2>#20074</2>
Spanish:
[<0>1bdd3b0dcf</0>] - <1>tools</1>: mejorar la detección de tipos de encabezados en json.js (Vse Mozhet Byt) <2>#20074</2>
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: 1258.
- The total amount of words translated in this project (as a Da-vinci/Utopian translator) is: 22822.
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.
Proof of Authorship
This translation was made on November 13th, 2018. 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].
