gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

chore(i18n,docs): update translations (#43306)

Browse Source
This commit is contained in:
camperbot
2021-08-26 21:50:40 -07:00
committed by GitHub
parent 9d466b36f5
commit ef6604f69e
45 changed files with 97 additions and 98 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/i18n/espanol/FAQ.md
View File

@@ -8,7 +8,7 @@ Yes - You can contribute to any of the 30+ languages we have enabled on our tran
We have the user contributed translations live in Chinese (中文) and Spanish (Español). We intend to localize freeCodeCamp into several major world languages. You can read all about this in our [announcement here](https://www.freecodecamp.org/news/world-language-translation-effort).
If you are interested in contributing to translations please makes sure you [read this guide](/how-to-translate-files) first.
If you are interested in contributing to translations please makes sure you [read this guide](how-to-translate-files.md) first.
### ¿Cómo puedo reportar un nuevo error?

2
docs/i18n/espanol/codebase-best-practices.md
View File

@@ -2,7 +2,7 @@
## General JavaScript
In most cases, our [linter](how-to-setup-freecodecamp-locally?id=follow-these-steps-to-get-your-development-environment-ready) will warn of any formatting which goes against this codebase's preferred practice.
In most cases, our [linter](how-to-setup-freecodecamp-locally.md#follow-these-steps-to-get-your-development-environment-ready) will warn of any formatting which goes against this codebase's preferred practice.
It is encouraged to use functional components over class-based components.

6
docs/i18n/espanol/how-to-open-a-pull-request.md
View File

@@ -2,7 +2,7 @@
Una pull request (PR) le permite enviar cambios desde su bifurcación en GitHub al repositorio principal de freeCodeCamp.org. Una vez que haya hecho cambios en el código, puede seguir estas pautas para abrir un PR.
> [!NOTE] Tu PR debe ser en inglés. See [here](https://contribute.freecodecamp.org/#/index?id=translations) for how to contribute translations.
> [!NOTE] Tu PR debe ser en inglés. See [here](index.md#translations) for how to contribute translations.
## Prepara un buen título para tu PR
@@ -68,7 +68,7 @@ Algunos ejemplos de buenos títulos para PRs serían:
- Esto es muy importante cuando se hagan cambios que no sean solo ediciones del contenido de texto como documentación o una descripción de un desafío. Ejemplos de los cambios que necesitan pruebas en el entorno local incluyen JavaScript, CSS o HTML que podrían cambiar la funcionalidad o el diseño de una página.
- Si tu PR afecta el comportamiento de una página, debe ir acompañada de la correspondiente [pruebas de integración de Cypress](/how-to-add-cypress-tests).
- If your PR affects the behaviour of a page it should be accompanied by corresponding [Cypress integration tests](how-to-add-cypress-tests.md).
## Comentarios sobre pull requests
@@ -78,7 +78,7 @@ Nuestros moderadores ahora echarán un vistazo y te dejarán tus comentarios. Po
Y como siempre, siéntete libre de preguntar en la [categoría de 'Contribuidores' de nuestro foro](https://forum.freecodecamp.org/c/contributors) o [en la sala de chat de contribuidores](https://chat.freecodecamp.org/channel/contributors).
> [!TIP] Si quieres contribuir con más PRs, te recomendamos que leas las directrices ["haciendo cambios y sincronizando"](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally?id=making-changes-locally) para evitar la necesidad de borrar tu bifurcación.
> [!TIP] If you are to be contributing more pull requests, we recommend you read the [making changes and syncing](how-to-setup-freecodecamp-locally.md#making-changes-locally) guidelines to avoid having to delete your fork.
## Conflicto en un pull request

2
docs/i18n/espanol/how-to-proofread-files.md
View File

@@ -14,7 +14,7 @@ You should see the list of projects you have been granted access to. Select the
You should now see the list of available files. Choose your file by selecting the `Proofread` button on the right of that file, then choosing `Proofreading` from the drop-down menu that appears.
> [!NOTE] Si estás en la vista "workspace" pero quieres trabajar en [traducir un archivo](./how-to-translate-files.md) en lugar de corregirlo, puedes seleccionar la opción `Crowdsourcing` del menú desplegable.
> [!NOTE] If you are in this workspace view, but want to work on [translating a file](how-to-translate-files.md) instead of proofreading, you may select `Crowdsourcing` from the dropdown menu instead.
## Revisar traducciones

2
docs/i18n/espanol/how-to-setup-freecodecamp-locally.md
View File

@@ -14,7 +14,7 @@ Comience instalando el software de requisitos previos para su sistema operativo.
Apoyamos principalmente el desarrollo en sistemas basados en Linux y Unix. Nuestro personal y los colaboradores de la comunidad trabajan regularmente con el código base utilizando herramientas instaladas en Ubuntu y macOS.
También soportamos Windows 10 a través de WSL2, que puedes preparar [leyendo esta guía](/how-to-setup-wsl).
We also support Windows 10 via WSL2, which you can prepare by [reading this guide](how-to-setup-wsl.md).
Algunos miembros de la comunidad también desarrollan en Windows 10 nativamente con Git for Windows (Git Bash), y otras herramientas instaladas en Windows. No tenemos soporte oficial para dicha configuración en este momento, así que recomendamos usar WSL2 en su lugar.

4
docs/i18n/espanol/how-to-setup-wsl.md
View File

@@ -6,7 +6,7 @@
>
> **Docker Desktop para Windows**: Vea los requisitos correspondientes para [Windows 10 Pro](https://docs.docker.com/docker-for-windows/install/#system-requirements) y [Windows 10 Home](https://docs.docker.com/docker-for-windows/install-windows-home/#system-requirements)
Esta guía cubre algunos pasos comunes con la configuración de WSL2. Once some of the common issues with WSL2 are addressed, you should be able to follow [this local setup guide](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally) to work with freeCodeCamp on Windows running a WSL distro like Ubuntu.
Esta guía cubre algunos pasos comunes con la configuración de WSL2. Once some of the common issues with WSL2 are addressed, you should be able to follow [this local setup guide](how-to-setup-freecodecamp-locally.md) to work with freeCodeCamp on Windows running a WSL distro like Ubuntu.
## Habilitar WSL
@@ -119,7 +119,7 @@ npm install -g npm@latest
## Configurar freeCodeCamp localmente
Now that you have installed the pre-requisites, follow [our local setup guide](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally) to clone, install and setup freeCodeCamp locally on your machine.
Now that you have installed the pre-requisites, follow [our local setup guide](how-to-setup-freecodecamp-locally.md) to clone, install and setup freeCodeCamp locally on your machine.
> [!WARNING]
>

2
docs/i18n/espanol/how-to-work-on-coding-challenges.md
View File

@@ -476,7 +476,7 @@ You are also able to test one challenge individually by performing the following
```
npm run test -- -g challenge-title-goes-here ```
Once you have verified that each challenge you've worked on passes the tests, [please create a pull request](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/docs/how-to-open-a-pull-request.md).
Once you have verified that each challenge you've worked on passes the tests, [please create a pull request](how-to-open-a-pull-request.md).
> [!TIP] You can set the environment variable `LOCALE` in the `.env` to the language of the challenge(s) you need to test.
>

6
docs/i18n/espanol/how-to-work-on-localized-client-webapp.md
View File

@@ -2,13 +2,13 @@
The react based client web app that powers our learning platform is built using Gatsby. It is translated into various world languages using [react-i18next](https://react.i18next.com/) and [i18next](https://www.i18next.com/).
You can learn more about setting up the client application locally for development by following [our local setup guide here](/how-to-setup-freecodecamp-locally). By default the application is available only in English.
You can learn more about setting up the client application locally for development by following [our local setup guide here](how-to-setup-freecodecamp-locally.md). By default the application is available only in English.
Once you have setup the project locally you should be able to follow this documentation to run the client in the language of your choice from the list of available languages.
This could be helpful when you are working on a feature that specifically targets something that involves localization, and requires you to validate for instance a button's label in a different language.
> [!TIP] You do not need to follow this document for translating freeCodeCamp's curriculum or contributing documentation. Read [this guide here](./how-to-translate-files.md) instead.
> [!TIP] You do not need to follow this document for translating freeCodeCamp's curriculum or contributing documentation. Read [this guide here](how-to-translate-files.md) instead.
Let's understand how the i18n frameworks and tooling work.
@@ -67,7 +67,7 @@ Some of these files are translated on our translation platform (Crowdin), some a
- The `intro.json` file contains the key-value pairs for the introduction text on the certification pages.
If you want to add/update translations for the keys please [read this guide here](/how-to-translate-files.md).
If you want to add/update translations for the keys please [read this guide here](how-to-translate-files.md).
**Files NOT translated on our translations platform:**

6
docs/i18n/espanol/how-to-work-on-practice-projects.md
View File

@@ -12,7 +12,7 @@ If you want to create new steps, the following tools simplify that process.
A one-off script that will automatically add the next step based on the last step numbered as `part-xxx.md` where `xxx` represents the 3-digit step number of the last step. The challenge seed code will use the previous step's challenge seed code with the editable region markers (ERMs) removed.
**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps).
**Note:** This script also runs [reorder-steps](#reorder-steps).
### How to run script:
@@ -27,7 +27,7 @@ npm run create-next-step
A one-off script that automatically adds a specified number of steps at a specific starting step number. The challenge seed code for all steps created will be empty.
**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps).
**Note:** This script also runs [reorder-steps](#reorder-steps).
### How to run script:
@@ -42,7 +42,7 @@ npm run create-empty-steps start=X num=Y # where X is the starting step number a
A one-off script that automatically adds a new step between two existing consecutive steps. The challenge seed code will use the existing starting step's challenge seed code with the editable region markers (ERMs) removed.
**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps).
**Note:** This script also runs [reorder-steps](#reorder-steps).
### How to run script:

2
docs/i18n/espanol/index.md
View File

@@ -10,7 +10,7 @@ Eres bienvenido a:
- Ayúdanos a corregir errores en la [plataforma de aprendizaje](#learning-platform) de freeCodeCamp.org.
- [Ayúdanos a traducir](#translations) freeCodeCamp.org a idiomas del mundo.
Respondemos a las preguntas más comunes sobre cómo contribuir [en nuestras preguntas frecuentes del contribuidor](/FAQ.md).
We answer the most common questions about contributing [in our contributor FAQ](FAQ.md).
## Plan de estudios

14
docs/i18n/espanol/moderator-handbook.md
View File

@@ -18,7 +18,7 @@ freeCodeCamp is an inclusive community, and we need to keep it that way.
We have a single code of conduct that governs our entire community. The fewer the rules, the easier they are to remember. You can read those rules and commit them to memory [here](https://code-of-conduct.freecodecamp.org).
> [!NOTE] As a moderator we would add you to one or more teams on GitHub, our community forum(s) & chat servers. If you are missing access on a platform that you would like to moderate please [reach out to a staff member](/FAQ?id=additional-assistance).
> [!NOTE] As a moderator we would add you to one or more teams on GitHub, our community forum(s) & chat servers. If you are missing access on a platform that you would like to moderate please [reach out to a staff member](FAQ.md#additional-assistance).
## Moderando GitHub
@@ -39,7 +39,7 @@ You can help us organize and triage the issue reports by applying labels from [t
Please pay special attention to the labels `"help wanted"` and `"first timers only"`. These are to be added to threads that you think can be opened up to potential contributors for making a pull request.
A `"first timer only"` label should be applied to a trivial issue (ex. a typo fix) and should include additional information. You can use this [reply template](/moderator-handbook?id=first-timer-only-issues) for triage.
A `"first timer only"` label should be applied to a trivial issue (ex. a typo fix) and should include additional information. You can use this [reply template](moderator-handbook.md#first-timer-only-issues) for triage.
#### Closing Stale, Outdated, Inactive Issues and Pull Requests
@@ -49,7 +49,7 @@ A `"first timer only"` label should be applied to a trivial issue (ex. a typo fi
- If the contributor asks for additional assistance or even time, the above can be relaxed and revisited after a response is given. In any case, the mods should use their best judgment to resolve the outstanding PR's status.
> [!TIP] We recommend you use this list of standard [reply templates](https://contribute.freecodecamp.org/#/moderator-handbook?id=reply-templates) while triaging issues.
> [!TIP] We recommend you use this list of standard [reply templates](moderator-handbook.md#reply-templates) while triaging issues.
### Moderating Pull Requests
@@ -63,7 +63,7 @@ Pull Requests (PRs) are how contributors submit changes to freeCodeCamp's reposi
You can also review these right on GitHub and decide whether to merge them. We need to be a bit more careful about these because millions of people will encounter this text as they work through the freeCodeCamp curriculum. Does the pull request make the text more clear without making it much longer? Are the edits relevant and not overly pedantic? Remember that our goal is for challenges to be as clear and as short as possible. They aren't the place for obscure details. Contributors may try to add links to resources to the challenges.
You can close invalid pull requests and reply to them with these [reply templates](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests).
You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests).
If the change looks good, please ensure to leave an approval with a "LGTM" comment. Once a pull request gets at least two approvals (including yours) from the moderators or the dev-team, you can go ahead and merge it.
@@ -75,7 +75,7 @@ Pull Requests (PRs) are how contributors submit changes to freeCodeCamp's reposi
Some contributors may try to add additional tests to cover pedantic corner-cases. We need to be careful to not make the challenge too complicated. These challenges and their tests should be as simple and intuitive as possible. Aside from the algorithm challenges and interview prep section, learners should be able to solve each challenge within about 2 minutes.
You can close invalid pull requests and reply to them with these [reply templates](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests).
You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests).
If the change looks good, please ensure to leave an approval with a "LGTM" comment. Once a pull request gets at least two approvals (including yours) from the moderators or the dev-team, you can go ahead and merge it.
@@ -142,7 +142,7 @@ Often, a pull request will be low effort. You can usually tell this immediately
There are also situations where the contributor is trying to add a link to their website, include a library they created, or have a frivolous edit that doesn't help anyone but themselves.
You can close invalid pull requests and reply to them with these [reply templates](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests).
You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests).
#### Otras pautas para moderadores en GitHub
@@ -387,7 +387,7 @@ Once you resolve these issues, we will be able to review your PR and merge it.
---
Feel free to reference the [contributing guidelines](https://contribute.freecodecamp.org/#/how-to-work-on-coding-challenges?id=testing-challenges) for instructions on running the CI build locally. ✅
Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅
```
### Syncing Fork