@@ -11,7 +11,7 @@ They are built by `docsbuild-scripts
11
11
<https://github.com/python/docsbuild-scripts/> `__ and hosted on
12
12
docs.python.org. There are several documentation translations already
13
13
in production; others are works in progress. See `the dashboard
14
- <https://m-aciek .github.io/pydocs-translation- dashboard/> `__ for
14
+ <https://python-docs-translations .github.io/dashboard/> `__ for
15
15
details.
16
16
17
17
.. list-table ::
@@ -113,20 +113,21 @@ First subscribe to the `translation mailing list <translation_ml_>`_,
113
113
and introduce yourself and the translation you're starting. Translations
114
114
fall under the aegis of the `PSF Translation Workgroup <translation_wg _>`_
115
115
116
- Then you can bootstrap your new translation by using our `cookiecutter
117
- <https://github.com/JulienPalard/python-docs-cookiecutter> `__.
116
+ Then you can bootstrap your new translation by using `cookiecutter
117
+ <https://github.com/JulienPalard/python-docs-cookiecutter> `__ or
118
+ `bootstrapper <https://github.com/python-docs-translations/python-docs-bootstrapper >`__.
118
119
119
120
The important steps look like this:
120
121
121
- - Create the GitHub repo (anywhere) with the right hierarchy (using the
122
- cookiecutter ).
122
+ - Create the GitHub repo (anywhere) with the right hierarchy (using one
123
+ of the bootstrappers ).
123
124
- Gather people to help you translate. You can't do it alone.
124
125
- You can use any tool to translate, as long as you can synchronize with Git.
125
126
Some use Transifex, and some use only GitHub. You can choose another
126
127
way if you like; it's up to you.
127
128
- Ensure we update this page to reflect your work and progress, either via a
128
129
PR or by asking on the `translation mailing list <translation_ml _>`_.
129
- - When ``bugs.html ``, ``tutorial ``, and ``library/functions `` are 100%
130
+ - When ``bugs ``, ``tutorial ``, and ``library/functions `` are 100%
130
131
completed, ask on the `translation mailing list <translation_ml _>`_ for
131
132
your language to be added in the language switcher on docs.python.org.
132
133
@@ -184,6 +185,10 @@ Here's what we're using:
184
185
- :pypi: `potodo ` to list what needs to be translated.
185
186
- :pypi: `sphinx-lint ` to validate reST syntax in translation files.
186
187
188
+ More related tools and projects can be found in the
189
+ `python-docs-translations `__ organisation on GitHub.
190
+
191
+ __ https://github.com/python-docs-translations
187
192
188
193
How is a coordinator elected?
189
194
-----------------------------
0 commit comments