You can take a look at their Crowdin project here.
- Translation Overview
This is the 48th translation I made for the Node.js project, and on this contribution I continued translating the PULL-REQUESTS.MD folder. Such folder I define it as follows:
-- PULL-REQUESTS.MD: This folder's intention is to show the collaborators how to exactly create a pull request. It shows all the steps one has to follow in order to do so and also the steps taken for that request to be either accepted or denied. The whole tutorial is made out of 10 steps, and after that it advises how to properly review every single detail of the PR.
On this contribution there were not found any complex terms that needed further information in order to be translated properly. However, I found a term that I had not knowledge of and I would like to share it with you.
The term is Lint. It refers to a process or a tool that analyzes sorce code by running a program to flag programming errors, bugs, stylistic errors and suspicious constructs. It is also known as linter, and the term was the name originally given to a particular software that could flag some suspicious and non-portable constructs (mostly bugs) in C language source code. Currently the term is applied generically to any tool, program or software that can do so in software written in any computer language.
Now, why is it important or what makes the linter useful? Well, it does not only help you to detect errors (or things that may look like), but it also helps you to avoid them.
A linter will help you catch bugs in a few scenarios. Let's take a look at some examples:
Detecting these errors while we write the code and not when we execute the app will save a lot of time, that could be a huge amount of time if the app is running in production. We could literally spend hours debugging in the worst case, but with a linter we get immediate feedback.
There are plenty of ways to use a linter. Let's look at some of them:
-- Using a plugin in your text editor: to get immediate feedback, just add a linter plugin to your text editor.
-- Create an NPM script: add your linter as a dev dependency in your package.json.
-- Git hook: use lint-staged with husky or pre-commit, or just have a small script that is invoked on a standard git pre-commit.
Examples of strings translated:
1. EN: Approval and Request Changes Workflow
SP: Flujo de Trabajo de Aprobación y Solicitud de Cambios
2. EN: If you happen to make a mistake in any of your commits, do not worry.
SP: Si comete un error en cualquiera de sus commits, no se preocupe.
3. EN: GitHub will automatically update the Pull Request.
SP: GitHub actualizará automáticamente la Pull Request.
-- Daily JS. Why you should always use a Linter? (https://medium.com/dailyjs/why-you-should-always-use-a-linter-and-or-pretty-formatter-bb5471115a76)
-- Wikipedia. Lint (https://en.wikipedia.org/wiki/Lint_(software))
-- Stack Overflow. Lint (https://stackoverflow.com/questions/8503559/what-is-linting)
I translated from English to Spanish.
I have translated over 100,000 words utilizing the Crowdin platform and this has given me experience to always grant great quality translations.
- Word Count
I have translated 1,052 words. This contribution has been made between the dates Feb/16/2019 and Feb/19/2019, when I realized the translation, and Feb/20/2019, when I realized the corrections.
Previous translations on this project:
- Part 1
- Part 2
- Part 3
- Part 4
- Part 5
- Part 6
- Part 7
- Part 8
- Part 9
- Part 10
- Part 11
- Part 12
- Part 13
- Part 14
- Part 15
- Part 16
- Part 17
- Part 18
- Part 19
- Part 20
- Part 21
- Part 22
- Part 23
- Part 24
- Part 25
- Part 26
- Part 27
- Part 28
- Part 29
- Part 30
- Part 31
- Part 32
- Part 33
- Part 34
- Part 35
- Part 36
- Part 37
- Part 38
- Part 39
- Part 40
- Part 41
- Part 42
- Part 43
- Part 44
- Part 45
- Part 46
- Part 47
Proof of Authorship