You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TRANSLATING.md
+8-12
Original file line number
Diff line number
Diff line change
@@ -72,10 +72,10 @@ You can find a list of the two-letter Sphinx language option [here](https://www.
72
72
73
73
The translation files contain the original English text and a space for you to enter the translated text. Before starting to translate, you need to make sure the translation files are up to date with the latest changes to the guide.
74
74
75
-
You can do this by running the following command:
75
+
You can do this by running the following command, replacing LANG by the language code you plan to work on (e.g., `es` for Spanish):
76
76
77
77
```shell
78
-
$ nox -s update-translations
78
+
$ nox -s update-language -- LANG
79
79
```
80
80
81
81
This command will create the translation files if they don't exist yet, or update them with the latest changes if they already exist.
@@ -220,10 +220,10 @@ When working on a translation, you **should not** modify the original English te
220
220
221
221
## Building the Translated Documentation
222
222
223
-
Once you finished translating or when you want to check the translation in context, you can build the guide locally on your computer, using the following command:
223
+
Once you finished translating or when you want to check the translation in context, you can build the guide locally on your computer, using the following command, replacing LANG by the proper language code (e.g., `es` for Spanish)
224
224
225
225
```shell
226
-
nox -s build-translations
226
+
nox -s build-language -- LANG
227
227
```
228
228
229
229
This command will build all the translated versions of the guide defined in the `LANGUAGES` list in `noxfile.py`. These translations will be stored in the `_build/html`, in folders named after the language code (e.g., `es`, `fr`, etc.).
@@ -251,7 +251,7 @@ You can follow these steps:
251
251
1. Build the translations of the guide with same parameters that will be used during the release:
252
252
253
253
```shell
254
-
nox -s build-translations-test
254
+
nox -s build-all-languages-test
255
255
```
256
256
257
257
2. Make sure there are no warnings or errors in the output. If there are, you will need to fix them before submitting the PR.
@@ -297,7 +297,7 @@ When you run the `sphinx-intl stat` command, you will see a list of `.po` files
297
297
298
298
### What happens when a string has changed in the original English text?
299
299
300
-
If a string has changed in the original English version, it will be marked as `fuzzy` in the translation file the next time it is updated (`nox -s update-translations`). Contributors working on the translation can then review the fuzzy entries and make the necessary changes to ensure it is accurate, before removing the `fuzzy` tag.
300
+
If a string has changed in the original English version, it will be marked as `fuzzy` in the translation file the next time it is updated (`update-language`, `update-all-languages`, or `update-all-release-languages`). Contributors working on the translation can then review the fuzzy entries and make the necessary changes to ensure it is accurate, before removing the `fuzzy` tag.
301
301
302
302
### How do I handle links in the translated text?
303
303
@@ -340,10 +340,6 @@ TODO: There are many approaches here, some projects release a translation as soo
340
340
341
341
### How can I get help with my translation?
342
342
343
-
If you have any questions or need help with your translation, you can create an issue in the repository.
343
+
If you have any questions or need help with your translation, you can create an [issue](https://github.com/pyOpenSci/python-package-guide/issues) in the [Packaging Guide repository](https://github.com/pyOpenSci/python-package-guide)
344
344
345
-
TODO: Maybe [Discourse](https://pyopensci.discourse.group/) could be used as a way for contributors to ask for help with translations or the translation workflow?
346
-
347
-
```
348
-
349
-
```
345
+
You can also ask in the PyOpenSci Discord server ([click here](https://discord.gg/CvSMp4zcqX) to join), you will find a general channel for questions related to our workflow, processes, and tools (translation-general) and channels for each of the languages we are working on (spanish-translation, japanese-translation, etc).
0 commit comments