@@ -4,7 +4,7 @@ French Translation of the Python Documentation
4
4
.. image :: https://travis-ci.org/python/python-docs-fr.svg?branch=3.7
5
5
:target: https://travis-ci.org/python/python-docs-fr
6
6
7
- **Translated: 33 % **
7
+ **Translated: 35 % **
8
8
9
9
Documentation Contribution Agreement
10
10
------------------------------------
@@ -77,7 +77,7 @@ Step by step:
77
77
All the translations must be made on the latest release.
78
78
We never translate on an oldest version, by example, the latest python release
79
79
is python 3.7, we don't want to translate directly on the python 3.5 release.
80
- If needed translations would be backported on the oldest versions by the
80
+ If needed translations would be backported on the oldest versions by the
81
81
`documentation team <https://www.python.org/dev/peps/pep-8015/#documentation-team> `.
82
82
83
83
Now you're ready to start a work session, each time you'll start a new task, start here:
@@ -93,22 +93,6 @@ Now you're ready to start a work session, each time you'll start a new task, sta
93
93
# You can now work on the file, typically using poedit,
94
94
poedit directory/file.po
95
95
96
- # After writing your changes to disk, check for correctness:
97
- make
98
-
99
- # Sphinx will tell you if there is any syntax error in the files
100
- # you modified. Note that in the French Translation, we try to keep Sphinx
101
- # warnings to zero.
102
-
103
- # you may want to check if there are semantic errors.
104
- # Open the translated file in your browser to check how it renders.
105
- # Don't forget to verify the typography. The French conventions are not
106
- # the English ones, especially for punctuation.
107
- # Also, Grammalecte, a browser plugin avaliable in your browser store,
108
- # is your friend even if, because of the technical words that appear
109
- # everywhere in the documentation, it points out many false positive.
110
- exo-open ../cpython/Doc/build/html/directory/file.html
111
-
112
96
# When everything is clear (syntax errors from Sphinx, html rendering,
113
97
# semantics, typography),
114
98
# you can commit your work with a nice explicit message:
@@ -121,7 +105,8 @@ Now you're ready to start a work session, each time you'll start a new task, sta
121
105
# it's nice as it's exactly what we want:
122
106
git push origin HEAD
123
107
124
- # Now you can open the pull request on github, just go to
108
+ # The previous command will print you a link to open a PR on github.
109
+ # If you missed it, just go to
125
110
# https://github.com/python/python-docs-fr/ and a nice "Compare & pull request"
126
111
# button should appear after a few seconds telling you can ask for a pull request.
127
112
@@ -251,6 +236,7 @@ e.g. e.g. (pour *exempli gratia*)
251
236
garbage collector ramasse-miettes
252
237
identifier identifiant
253
238
immutable immuable
239
+ installer installateur
254
240
interpreter interpréteur
255
241
library bibliothèque
256
242
list comprehension liste en compréhension (liste en intension est
@@ -316,7 +302,7 @@ Maintenance
316
302
317
303
All those snippets are to run from the root of a ` ` python-docs-fr` `
318
304
clone, and some expect to find an up-to-date CPython clone near to it,
319
- like::
305
+ like:
320
306
321
307
.. code-block:: bash
322
308
@@ -361,7 +347,7 @@ Run a test build locally
361
347
Synchronize translation with Transifex
362
348
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
363
349
364
- You'll need the ` ` transifex-client` ` and ` ` poindent ` `
350
+ You'll need the ` ` transifex-client` ` and ` ` powrap ` `
365
351
from Pypi.
366
352
367
353
You'll need to configure ` ` tx` ` via ` ` tx init` ` if not already done.
@@ -374,6 +360,6 @@ You'll need to configure ``tx`` via ``tx init`` if not already done.
374
360
pomerge --from-files **/*.po
375
361
git checkout -- .
376
362
pomerge --to-files **/*.po
377
- poindent --modified
363
+ powrap --modified
378
364
git commit -m "tx pull"
379
365
tx push -t -f
0 commit comments