From 04b5f4c4157f55eb7310345bf49daaf53285808b Mon Sep 17 00:00:00 2001 From: Maciej Olko Date: Tue, 4 Feb 2025 23:04:47 +0100 Subject: [PATCH 1/7] Update the link to the translations dashboard --- documentation/translating.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/translating.rst b/documentation/translating.rst index 9e90a01d5..b256ccb77 100644 --- a/documentation/translating.rst +++ b/documentation/translating.rst @@ -11,7 +11,7 @@ They are built by `docsbuild-scripts `__ and hosted on docs.python.org. There are several documentation translations already in production; others are works in progress. See `the dashboard -`__ for +`__ for details. .. list-table:: From ad362aa60c0d287fa09648f19a78feea836f8060 Mon Sep 17 00:00:00 2001 From: Maciej Olko Date: Thu, 13 Feb 2025 23:28:07 +0100 Subject: [PATCH 2/7] Mention Ege Eakman's bootstrapper project --- documentation/translating.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/documentation/translating.rst b/documentation/translating.rst index b256ccb77..239ffd01d 100644 --- a/documentation/translating.rst +++ b/documentation/translating.rst @@ -112,13 +112,14 @@ First subscribe to the `translation mailing list `_, and introduce yourself and the translation you're starting. Translations fall under the aegis of the `PSF Translation Workgroup `_ -Then you can bootstrap your new translation by using our `cookiecutter -`__. +Then you can bootstrap your new translation by using `cookiecutter +`__ or +`bootstrapper `__. The important steps look like this: -- Create the GitHub repo (anywhere) with the right hierarchy (using the - cookiecutter). +- Create the GitHub repo (anywhere) with the right hierarchy (using one + of bootstrappers). - Gather people to help you translate. You can't do it alone. - You can use any tool to translate, as long as you can synchronize with Git. Some use Transifex, and some use only GitHub. You can choose another From bbdbf28a2f179e65899f5779c5c99ac3d5568114 Mon Sep 17 00:00:00 2001 From: Maciej Olko Date: Thu, 13 Feb 2025 23:28:54 +0100 Subject: [PATCH 3/7] Remove suffix from chapter name in PEP 545 section --- documentation/translating.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/translating.rst b/documentation/translating.rst index 239ffd01d..d33e1cddc 100644 --- a/documentation/translating.rst +++ b/documentation/translating.rst @@ -126,7 +126,7 @@ The important steps look like this: way if you like; it's up to you. - Ensure we update this page to reflect your work and progress, either via a PR or by asking on the `translation mailing list `_. -- When ``bugs.html``, ``tutorial``, and ``library/functions`` are 100% +- When ``bugs``, ``tutorial``, and ``library/functions`` are 100% completed, ask on the `translation mailing list `_ for your language to be added in the language switcher on docs.python.org. From 2f787b02fba2fce7f25846a0c9b9fe57b57f05ff Mon Sep 17 00:00:00 2001 From: Maciej Olko Date: Thu, 13 Feb 2025 23:39:11 +0100 Subject: [PATCH 4/7] Add a mention about the new organisation in tools FAQ section --- documentation/translating.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/documentation/translating.rst b/documentation/translating.rst index d33e1cddc..27546e749 100644 --- a/documentation/translating.rst +++ b/documentation/translating.rst @@ -184,6 +184,8 @@ Here's what we're using: - :pypi:`potodo` to list what needs to be translated. - :pypi:`sphinx-lint` to validate reST syntax in translation files. +Some related tools and projects can be found in +`python-docs-translations organisation on GitHub `__. How is a coordinator elected? ----------------------------- From 9b2d03352f3ebc7669fbea107ac707e3451f7467 Mon Sep 17 00:00:00 2001 From: Maciej Olko Date: Thu, 13 Feb 2025 23:39:58 +0100 Subject: [PATCH 5/7] Improve the mention about the new organisation in tools FAQ section --- documentation/translating.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/translating.rst b/documentation/translating.rst index 27546e749..905576619 100644 --- a/documentation/translating.rst +++ b/documentation/translating.rst @@ -184,7 +184,7 @@ Here's what we're using: - :pypi:`potodo` to list what needs to be translated. - :pypi:`sphinx-lint` to validate reST syntax in translation files. -Some related tools and projects can be found in +More related tools and projects can be found in `python-docs-translations organisation on GitHub `__. How is a coordinator elected? From 9e552af349a793e0c1cefbb81e899908f7a5b0cf Mon Sep 17 00:00:00 2001 From: Maciej Olko Date: Tue, 18 Feb 2025 12:50:03 +0100 Subject: [PATCH 6/7] Update documentation/translating.rst: improve wording Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com> --- documentation/translating.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/translating.rst b/documentation/translating.rst index 905576619..3e82268a3 100644 --- a/documentation/translating.rst +++ b/documentation/translating.rst @@ -119,7 +119,7 @@ Then you can bootstrap your new translation by using `cookiecutter The important steps look like this: - Create the GitHub repo (anywhere) with the right hierarchy (using one - of bootstrappers). + of the bootstrappers). - Gather people to help you translate. You can't do it alone. - You can use any tool to translate, as long as you can synchronize with Git. Some use Transifex, and some use only GitHub. You can choose another From b2e9a386a9928406aea0c3c5ab5387ee98401976 Mon Sep 17 00:00:00 2001 From: Maciej Olko Date: Thu, 27 Feb 2025 15:08:14 +0100 Subject: [PATCH 7/7] Narrow down translations organisation link text Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com> --- documentation/translating.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/documentation/translating.rst b/documentation/translating.rst index 3e82268a3..471f9014e 100644 --- a/documentation/translating.rst +++ b/documentation/translating.rst @@ -184,8 +184,10 @@ Here's what we're using: - :pypi:`potodo` to list what needs to be translated. - :pypi:`sphinx-lint` to validate reST syntax in translation files. -More related tools and projects can be found in -`python-docs-translations organisation on GitHub `__. +More related tools and projects can be found in the +`python-docs-translations`__ organisation on GitHub. + +__ https://github.com/python-docs-translations How is a coordinator elected? -----------------------------