@@ -83,7 +83,27 @@ Now you're ready to start a work session, each time you'll start a new task, sta
83
83
git checkout -b glossary upstream/3.7
84
84
85
85
# You can now work on the file, typically using poedit,
86
- # then commit your work with a nice explicit message:
86
+ poedit directory/file.po
87
+
88
+ # After writing your changes to disk, check for correctness:
89
+ make
90
+
91
+ # Sphinx will tell you if there is any syntax error in the files
92
+ # you modified. Note that in the French Translation, we try to keep Sphinx
93
+ # warnings to zero.
94
+
95
+ # you may want to check if there are semantic errors.
96
+ # Open the translated file in your browser to check how it renders.
97
+ # Don't forget to verify the typography. The French conventions are not
98
+ # the English ones, especially for punctuation.
99
+ # Also, Grammalecte, a browser plugin avaliable in your browser store,
100
+ # is your friend even if, because of the technical words that appear
101
+ # everywhere in the documentation, it points out many false positive.
102
+ exo-open ../cpython/Doc/build/html/directory/file.html
103
+
104
+ # When everything is clear (syntax errors from Sphinx, html rendering,
105
+ # semantics, typography),
106
+ # you can commit your work with a nice explicit message:
87
107
git commit -a -m " Working on glossary."
88
108
89
109
# Then push your modifications to your github clone,
@@ -205,8 +225,8 @@ parameter paramètre
205
225
prompt invite
206
226
raise lever
207
227
regular expression expression rationnelle, expression régulière
208
- return renvoie, donne (On évite
209
- "retourne" qui pourrait porter à confusion.
228
+ return renvoie, donne (on évite
229
+ "retourne" qui pourrait porter à confusion) .
210
230
simple quote guillemet simple, apostrophe (apostrophe
211
231
is to glue, guillemet is to surround)
212
232
socket *socket *
0 commit comments