@@ -1586,11 +1586,11 @@ see the make targets above).
1586
1586
Translating
1587
1587
===========
1588
1588
1589
- Python documentation translations are governed by the :PEP: `545 `,
1590
- they are built by `docsbuild-scripts
1589
+ Python documentation translations are governed by :PEP: `545 `.
1590
+ They are built by `docsbuild-scripts
1591
1591
<https://github.com/python/docsbuild-scripts/> `__ and hosted on
1592
1592
docs.python.org. There are several documentation translations already
1593
- in production, other are work in progress:
1593
+ in production; others are works in progress.
1594
1594
1595
1595
+-----------------+-------------------------------+----------------------------+
1596
1596
| Language | Contact | Links |
@@ -1701,16 +1701,16 @@ fall under the aegis of the `PSF Translation Workgroup <translation_wg_>`_
1701
1701
Then you can bootstrap your new translation by using our `cookiecutter
1702
1702
<https://github.com/JulienPalard/python-docs-cookiecutter> `__.
1703
1703
1704
- The important steps looks like this:
1704
+ The important steps look like this:
1705
1705
1706
- - Create the github repo (anywhere), with the right hierarchy (using the
1706
+ - Create the GitHub repo (anywhere) with the right hierarchy (using the
1707
1707
cookiecutter).
1708
- - Gather people to help you translating, you can't do it alone.
1708
+ - Gather people to help you translate. You can't do it alone.
1709
1709
- You can use any tool to translate, as long as you can synchronize with git.
1710
- Some are using Transifex, some are using only github, or you can choose another
1711
- way, it's up to you.
1712
- - Ensure we updated this page to reflect your work and progress, either via a
1713
- PR, or by asking on the `translation mailing list <translation_ml _>`_.
1710
+ Some use Transifex, and some use only GitHub. You can choose another
1711
+ way if you like; it's up to you.
1712
+ - Ensure we update this page to reflect your work and progress, either via a
1713
+ PR or by asking on the `translation mailing list <translation_ml _>`_.
1714
1714
- When ``tutorial/ ``, ``bugs.py `` and ``library/functions ``
1715
1715
are complete, ask on the `translation mailing list <translation_ml _>`_ for your language to be added in the
1716
1716
language picker on docs.python.org.
@@ -1722,13 +1722,13 @@ PEP 545 summary:
1722
1722
Here are the essential points of :PEP: `545 `:
1723
1723
1724
1724
- Each translation is assigned an appropriate lowercased language tag,
1725
- with an optional region subtag, joined with a dash, like
1725
+ with an optional region subtag, and joined with a dash, like
1726
1726
``pt-br `` or ``fr ``.
1727
1727
1728
- - Each translation is under CC0 and marked as so in the README (as in
1728
+ - Each translation is under CC0 and marked as such in the README (as in
1729
1729
the cookiecutter).
1730
1730
1731
- - Translations files are hosted on
1731
+ - Translation files are hosted on
1732
1732
``https://github.com/python/python-docs-{LANGUAGE_TAG} `` (not
1733
1733
mandatory to start a translation, but mandatory to land on
1734
1734
``docs.python.org ``).
@@ -1749,62 +1749,61 @@ and there's a `Libera.Chat IRC <https://libera.chat/>`_ channel,
1749
1749
Translation FAQ
1750
1750
---------------
1751
1751
1752
- Which version of Python documentation should be translated?
1753
- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1752
+ Which version of the Python documentation should be translated?
1753
+ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1754
1754
1755
- Consensus is to work on current stable, you can then propagate your
1756
- translation from a branch to another using `pomerge
10000
1755
+ Consensus is to work on current stable. You can then propagate your
1756
+ translation from one branch to another using `pomerge
1757
1757
<https://pypi.org/project/pomerge/> `__.
1758
1758
1759
1759
1760
1760
Are there some tools to help in managing the repo?
1761
1761
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1762
1762
1763
- Here's what's we're using:
1763
+ Here's what we're using:
1764
1764
1765
- - `pomerge <https://pypi.org/project/pomerge/ >`__ to propagate translation
1766
- from a files to others.
1767
- - `pospell <https://pypi.org/project/pospell/ >`__ to check for typo in po files.
1765
+ - `pomerge <https://pypi.org/project/pomerge/ >`__ to propagate translations
1766
+ from one file to others.
1767
+ - `pospell <https://pypi.org/project/pospell/ >`__ to check for typos in `` .po `` files.
1768
1768
- `powrap <https://pypi.org/project/powrap/ >`__ to rewrap the ``.po `` files
1769
- before committing, this helps keeping git diffs short.
1769
+ before committing. This helps keep git diffs short.
1770
1770
- `potodo <https://pypi.org/project/potodo/ >`__ to list what needs to be translated.
1771
1771
1772
1772
1773
-
1774
- How a coordinator is elected?
1773
+ How is a coordinator elected?
1775
1774
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1776
1775
1777
- There is no election, each translation have to sort this out. Here are some suggestions.
1776
+ There is no election; each translation has to sort this out. Here are some suggestions.
1778
1777
1779
1778
- Coordinator requests are to be public on the `translation mailing list <translation_ml _>`_.
1780
- - If the given language have a native core dev, the core dev have its
1781
- word on the choice.
1782
- - Anyone who wants to become coordinator for its native language, and shows
1783
- motivation by translating and building a community, will be named
1779
+ - If the given language has a native core dev, the core dev has their
1780
+ say on the choice.
1781
+ - Anyone who wants to become coordinator for their native language and shows
1782
+ motivation by translating and building a community will be named
1784
1783
coordinator.
1785
1784
- In case of concurrency between two persons, no one will sort this out
1786
- for you. It is up to you two to organize a local election or whatever
1785
+ for you. It is up to you two to organize a local election or whatever is
1787
1786
needed to sort this out.
1788
- - In case a coordinator become inactive or unreachable for a long
1787
+ - If a coordinator becomes inactive or unreachable for a long
1789
1788
period of time, someone else can ask for a takeover on the `translation mailing list <translation_ml _>`_.
1790
1789
1791
1790
1792
1791
The entry for my translation is missing/not up to date on this page
1793
- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1792
+ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1794
1793
1795
1794
Ask on the `translation mailing list <translation_ml _>`_, or better, make a PR on the `devguide
1796
1795
<https://github.com/python/devguide/> `__.
1797
1796
1798
1797
1799
- I have a translation, but not on git, what should I do?
1800
- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1798
+ I have a translation, but it's not in git. What should I do?
1799
+ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1801
1800
1802
1801
You can ask for help on the `translation mailing list <translation_ml _>`_, and
1803
1802
the team will help you create an appropriate repository. You can still use tools like transifex,
1804
1803
if you like.
1805
1804
1806
1805
1807
- My git hierarchy does not match yours, can I keep it?
1806
+ My git hierarchy does not match yours. Can I keep it?
1808
1807
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1809
1808
1810
1809
No, inside the ``github.com/python `` organization we’ll all have the
@@ -1813,10 +1812,11 @@ translations. So you may have to convert from one hierarchy to another.
1813
1812
Ask for help on the `translation mailing list <translation_ml _>`_ if you’re
1814
1813
not sure on how to do it.
1815
1814
1816
- What hierarchy should I use in my github repository?
1815
+
1816
+ What hierarchy should I use in my GitHub repository?
1817
1817
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1818
1818
1819
- As for every project, we have a *branch * per version. We store ``po ``
1819
+ As for every project, we have a *branch * per version. We store ``. po ``
1820
1820
files in the root of the repository using the ``gettext_compact=0 ``
1821
1821
style.
1822
1822
0 commit comments