1- Translation of the Python Documentation —bn_in
1+ Translation of the Python Documentation —bn-in
22===============================================
33
4- ..image ::https://travis-ci.org/python/python-docs-bn_in .svg?branch=3.12
5- :target: https://travis-ci.org/python/python-docs-bn_in
4+ ..image ::https://travis-ci.org/python/python-docs-bn-in .svg?branch=3.14
5+ :target: https://travis-ci.org/python/python-docs-bn-in
66
77
88Documentation Contribution Agreement
@@ -37,8 +37,9 @@ How to Contribute
3737You can contribute using:
3838
3939- Github
40- - `transifex <https://www.transifex.com/python-doc/public/ >`_
41- - Or just by opening `an issue on github <https://github.com/python/python-docs-bn_in/issues >`_
40+ - Or just by opening `an issue on github <https://github.com/python/python-docs-bn-in/issues >`_
41+
42+ We will use Weblate in future.
4243
4344
4445Contributing using Github
@@ -55,8 +56,8 @@ Prerequisites:
5556
5657Let's start:
5758
58- You'll need to fork the `python-docs-bn_in
59- <https://github.com/python/python-docs-bn_in > `_ clicking its ``Fork ``
59+ You'll need to fork the `python-docs-bn-in
60+ <https://github.com/python/python-docs-bn-in > `_ clicking its ``Fork ``
6061button. This creates a copy of the whole project on your github
6162account: a place where you have the rights to do modifications.
6263
@@ -65,17 +66,17 @@ Step by step:
6566..code-block ::bash
6667
6768# Git clone your github fork using ssh (replace JulienPalard):
68- git clone git@github.com:JulienPalard/python-docs-bn_in .git
69+ git clone git@github.com:JulienPalard/python-docs-bn-in .git
6970
7071# Go to the cloned directory:
71- cd python-docs-bn_in /
72+ cd python-docs-bn-in /
7273
7374# Add the upstream (the public repository) using HTTPS (won't ask for password):
74- git remote add upstream https://github.com/python/python-docs-bn_in .git
75+ git remote add upstream https://github.com/python/python-docs-bn-in .git
7576
7677
7778We never translate on an oldest version, by example, the latest Python release
78- is Python 3.12 , we don't want to translate directly on the Python 3.5 release.
79+ is Python 3.14 , we don't want to translate directly on the Python 3.5 release.
7980If needed translations would be backported on the oldest versions by the
8081`documentation team <https://www.python.org/dev/peps/pep-8015/#documentation-team >`_.
8182
@@ -84,10 +85,10 @@ Now you're ready to start a work session, each time you'll start a new task, sta
8485..code-block ::bash
8586
8687# To work, we'll need a branch, based on an up-to-date (freshly fetched)
87- # upstream/3.12 branch, let's say we'll work on glossary so we name
88+ # upstream/3.14 branch, let's say we'll work on glossary so we name
8889# the branch "glossary":
8990 git fetch upstream
90- git checkout -b glossary upstream/3.12
91+ git checkout -b glossary upstream/3.14
9192
9293# You can now work on the file, typically using poedit,
9394 poedit directory/file.po
@@ -106,7 +107,7 @@ Now you're ready to start a work session, each time you'll start a new task, sta
106107
107108# The previous command will print you a link to open a PR on github.
108109# If you missed it, just go to
109- # https://github.com/python/python-docs-bn_in / and a nice "Compare & pull request"
110+ # https://github.com/python/python-docs-bn-in / and a nice "Compare & pull request"
110111# button should appear after a few seconds telling you can ask for a pull request.
111112
112113# Now someone is reviewing your modifications, and you'll want to fix their
@@ -237,14 +238,14 @@ after ensuring ``~/.local/bin/`` is in your ``PATH``.
237238Maintenance
238239-----------
239240
240- All those snippets are to run from the root of a` ` bn_in ` `
241+ All those snippets are to run from the root of a` ` bn-in ` `
241242clone, and some expect to find an up-to-date CPython clone near to it,
242243like:
243244
244245.. code-block:: bash
245246
246247 ~/
247- ├── python-docs-bn_in /
248+ ├── python-docs-bn-in /
248249 └── cpython/
249250
250251To clone CPython you may use: