Skip to content

Expand section on no existing project #132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 22, 2025
Merged

Expand section on no existing project #132

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/commands.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ From inside your language repository, run:

.. code-block:: shell

BRANCH=|py_new|
BRANCH=3.13
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TBH, I didn't see you placed variables before merging the PR. Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You asked and I did:-)

git clone --depth 1 https://github.com/python/cpython --branch $BRANCH

Use ``--depth 1`` to shallow clone, which avoids downloading all the 800 MB of data
Expand Down Expand Up @@ -264,7 +264,7 @@ translations.
.. code-block:: shell

CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
TARGET_BRANCH=|py_last|
TARGET_BRANCH=3.12
pomerge --from-files *.po **/*.po
git checkout ${TARGET_BRANCH}
pomerge --to-files *.po **/*.po
Expand Down
23 changes: 16 additions & 7 deletions docs/new-translators.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,24 +17,33 @@ To ensure that translations are of a good standard, it is essential that you are
confident in both English and the translation language.

If you are new to the translation of Python documentation, we recommend that
you start by reading the Translating_ on `Python Developer's Guide`_
(a.k.a. devguide), joining the relevant contact channels (such as the `Docs Community`_
you start by reading the Translating_ in the `Python Developer's Guide`_
(a.k.a. *devguide*), joining the relevant contact channels (such as the `Docs Community`_
Discord ``#translations`` channel), and familiarizing yourself with `PEP 545`_.

If there is already a repository for your language team, please join and
introduce yourself.

**If there is no existing repository or language team, you will need to create
one.** Simply translating on Transifex is not enough to have your language
published in the Python documentation. Please follow the instructions on starting
a new translation.

.. _Translating: https://devguide.python.org/documentation/translating/
.. _Python Developer's Guide: https://devguide.python.org
.. _PEP 545: https://peps.python.org/pep-0545/
.. _Docs Community: https://docs-community.readthedocs.io/


There is no existing project for my language
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**If there is no existing repository or language team, you will need to create
one.** Simply translating on Transifex is not enough to have your language
published in the Python documentation.

There are several languages on Transifex that are not connected to a repository,
please confirm this is not the case before you begin translating. You can verify
by checking there is an in entry in the Translating_ section of the `devguide <Python Developer's Guide>`_.

To start a new translation follow the guide `here <https://devguide.python.org/documentation/translating/#starting-a-new-translation>`_.


Getting to Know Transifex
~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down