# Localization of The Pipx Documentation

**URL:** <https://localizethedocs.discourse.group/t/localization-of-the-pipx-documentation/84>\
**Category:** Announcement\
**Created:** [October 7, 2026, 8:11am UTC](https://localizethedocs.discourse.group/t/localization-of-the-pipx-documentation/84 "2026-10-07T08:11:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![localizethedocs](https://yyz2.discourse-cdn.com/flex036/user_avatar/localizethedocs.discourse.group/localizethedocs/32/8_2.png) [@localizethedocs](https://localizethedocs.discourse.group/u/localizethedocs)\
**Post date:** [October 7, 2026, 8:11am UTC](https://localizethedocs.discourse.group/t/localization-of-the-pipx-documentation/84/1 "2026-10-07T08:11:40Z")

</div>

### Announcement

We’re glad to announce that the 🎉 **pipx-docs-l10n** 🎉 project is now published:

- 🚀 **Preview:** [pipx-docs-l10n](https://projects.localizethedocs.org/pipx-docs-l10n)
- 🌐 **Crowdin:** [pipx-docs-l10n](https://localizethedocs.crowdin.com/pipx-docs-l10n)
- 🐙 **GitHub:** [pipx-docs-l10n](https://github.com/localizethedocs/pipx-docs-l10n)

The goal of this project is to translate [The Pipx Documentation](https://pipx.pypa.io/) into multiple languages. Translations are contributed via the Crowdin platform, automatically synchronized with the GitHub repository, and can be previewed on GitHub Pages.

### How to Contribute Translations?

To contribute the translations, please follow the following steps:

1. Create an account on [Crowdin Enterprise](https://localizethedocs.crowdin.com/u/signup) if you don’t have one.
2. Log in and go to the [pipx-docs-l10n](https://localizethedocs.crowdin.com/pipx-docs-l10n) project.
3. Choose the target language you would like to contribute.

If the target language is not yet supported, please open an issue to [request the new language](https://github.com/localizethedocs/pipx-docs-l10n/issues/new?template=language_request.yml). Once the requested language is added, you can start translating.

### How to Reuse Translations?

If the upstream project or anyone wants to reuse the `.po` files maintained by the this project, they can download the `.po` files from the `po/<version>` branch with the following command:

```bash
git clone --branch=po/<version> https://github.com/localizethedocs/pipx-docs-l10n.git <locale-dir>

```

Those `po/<version>` branches are created to facilitate reusage by the upstream project. For instance, the `zh_TW` documentation for the `latest` version can be generated using the demo commands below:

> **Click to expand the demo commands**
>
> ```bash
> BRANCH=main
> VERSION=latest
> LANGUAGE=zh_TW
> BUILDER=html
> REPODIR=$(pwd)/pipx-docs
> VENVDIR=$REPODIR/.venv
> 
> # Prepare the repository and environment
> git clone --branch=$BRANCH --recurse-submodules https://github.com/pypa/pipx.git $REPODIR
> cd $REPODIR
> conda create --prefix $VENVDIR --yes
> conda activate $VENVDIR
> export PYTHONNOUSERSITE=1
> conda install python=3.14 -c conda-forge -c nodefaults --yes
> python -m ensurepip
> python -m pip install . --group docs
> 
> # Clone the .po files to the 'locale' directory
> git clone --branch=po/$VERSION https://github.com/localizethedocs/pipx-docs-l10n.git docs/locale
> 
> # Build the documentation
> pushd docs
> sphinx-build \
> -b $BUILDER \
> -D language=$LANGUAGE \
> -D locale_dirs=locale \
> -D gettext_compact=0 \
> -D gettext_additional_targets=index,literal-block,raw \
> . \
> ./_build/$LANGUAGE
> popd
> 
> # Preview the documentation
> firefox docs/_build/$LANGUAGE/index.html
> 
> ```
