Skip to content

Commit 9867120

Browse files
m-aciekStanFromIrelandAA-Turner
authored
Note the python-docs-translations GitHub organisation (#1507)
Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com> Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
1 parent f489bdd commit 9867120

File tree

1 file changed

+11
-6
lines changed

1 file changed

+11
-6
lines changed

documentation/translating.rst

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ They are built by `docsbuild-scripts
1111
<https://github.com/python/docsbuild-scripts/>`__ and hosted on
1212
docs.python.org. There are several documentation translations already
1313
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
1515
details.
1616

1717
.. list-table::
@@ -113,20 +113,21 @@ First subscribe to the `translation mailing list <translation_ml_>`_,
113113
and introduce yourself and the translation you're starting. Translations
114114
fall under the aegis of the `PSF Translation Workgroup <translation_wg_>`_
115115

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>`__.
118119

119120
The important steps look like this:
120121

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).
123124
- Gather people to help you translate. You can't do it alone.
124125
- You can use any tool to translate, as long as you can synchronize with Git.
125126
Some use Transifex, and some use only GitHub. You can choose another
126127
way if you like; it's up to you.
127128
- Ensure we update this page to reflect your work and progress, either via a
128129
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%
130131
completed, ask on the `translation mailing list <translation_ml_>`_ for
131132
your language to be added in the language switcher on docs.python.org.
132133

@@ -184,6 +185,10 @@ Here's what we're using:
184185
- :pypi:`potodo` to list what needs to be translated.
185186
- :pypi:`sphinx-lint` to validate reST syntax in translation files.
186187

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
187192

188193
How is a coordinator elected?
189194
-----------------------------

0 commit comments

Comments
 (0)