From 558c158f7580192a4749e3bdb425e0112397a7de Mon Sep 17 00:00:00 2001 From: Stan Ulbrych Date: Sun, 15 Jun 2025 11:44:32 +0100 Subject: [PATCH] Conflicts --- documentation/translations/coordinating.rst | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/documentation/translations/coordinating.rst b/documentation/translations/coordinating.rst index 3d64858ad..7568116c8 100644 --- a/documentation/translations/coordinating.rst +++ b/documentation/translations/coordinating.rst @@ -12,11 +12,13 @@ fall under the aegis of the `PSF Translation Workgroup `_ Then you can bootstrap your new translation by using `cookiecutter `__ or `bootstrapper `__. +You can also start your translation using `Transifex `_ +following this `guide `_. The important steps look like this: - Create the GitHub repo (any account) with the correct hierarchy by using one - of the bootstrappers. + of the bootstrappers or Transifex. - 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 @@ -58,11 +60,12 @@ Are there tools to help in managing the repo? Here's what we're using: -- :pypi:`pomerge` to propagate translations from one file to others. -- :pypi:`pospell` to check for typos in ``.po`` files. -- :pypi:`powrap` to rewrap the ``.po`` files - before committing. This helps keep Git diffs short. -- :pypi:`potodo` to list what needs to be translated. +- :pypi:`poutils` which includes: + - :pypi:`pomerge` to propagate translations from one file to others. + - :pypi:`pospell` to check for typos in ``.po`` files. + - :pypi:`powrap` to rewrap the ``.po`` files + before committing. This helps keep Git diffs short. + - :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 the