FIX msgids.

Author: JulienPalard

howto/clinic.po

@@ -325,7 +325,7 @@ msgstr ""
 
 #: howto/clinic.rst:159
 msgid ""
-"Find a Python builtin that calls either :c:func:`PyArg_ParseTuple` or :c:"
+"Find a Python builtin that calls either :c:func:`PyArg_ParseTuple` or :c:"
 "func:`PyArg_ParseTupleAndKeywords`, and hasn't been converted to work with "
 "Argument Clinic yet. For my example I'm using ``_pickle.Pickler.dump()``."
 msgstr ""
@@ -342,7 +342,7 @@ msgstr "Si l'appel à ``PyArg_Parse`` utilise l'un des formats suivants :"
 
 #: howto/clinic.rst:176
 msgid ""
-"or if it has multiple calls to :c:func:`PyArg_ParseTuple`, you should choose "
+"or if it has multiple calls to :c:func:`PyArg_ParseTuple`, you should choose "
 "a different function.  Argument Clinic *does* support all of these "
 "scenarios.  But these are advanced topics—let's do something simpler for "
 "your first function."
@@ -353,7 +353,7 @@ msgstr ""
 
 #: howto/clinic.rst:181
 msgid ""
-"Also, if the function has multiple calls to :c:func:`PyArg_ParseTuple` or :c:"
+"Also, if the function has multiple calls to :c:func:`PyArg_ParseTuple` or :c:"
 "func:`PyArg_ParseTupleAndKeywords` where it supports different types for the "
 "same argument, or if the function uses something besides PyArg_Parse "
 "functions to parse its arguments, it probably isn't suitable for conversion "
@@ -456,7 +456,7 @@ msgstr ""
 #: howto/clinic.rst:242
 msgid ""
 "The name of the class and module should be the same as the one seen by "
-"Python.  Check the name defined in the :c:type:`PyModuleDef` or :c:type:"
+"Python.  Check the name defined in the :c:type:`PyModuleDef` or :c:type:"
 "`PyTypeObject` as appropriate."
 msgstr ""
 "Le nom de la classe et du module doivent être les mêmes que ceux vus par "
@@ -467,7 +467,7 @@ msgstr ""
 msgid ""
 "When you declare a class, you must also specify two aspects of its type in "
 "C: the type declaration you'd use for a pointer to an instance of this "
-"class, and a pointer to the :c:type:`PyTypeObject` for this class."
+"class, and a pointer to the :c:type:`PyTypeObject` for this class."
 msgstr ""
 "Quand vous déclarez une classe, vous devez aussi spécifier deux aspects de "
 "son type en C : la déclaration de type que vous utiliseriez pour un pointeur "
@@ -497,7 +497,7 @@ msgstr ""
 #: howto/clinic.rst:283
 msgid ""
 "Argument Clinic's support for \"default values\" is quite sophisticated; "
-"please see :ref:`the section below on default values <default_values>` for "
+"please see :ref:`the section below on default values <default_values>` for "
 "more information."
 msgstr ""
 "Argument Clinic peut traiter les « valeurs par défaut » de manière assez "
@@ -529,7 +529,7 @@ msgid ""
 "quoted string.  (\"format unit\" is the formal name for the one-to-three "
 "character substring of the ``format`` parameter that tells the argument "
 "parsing function what the type of the variable is and how to convert it.  "
-"For more on format units please see :ref:`arg-parsing`.)"
+"For more on format units please see :ref:`arg-parsing`.)"
 msgstr ""
 "Pour chaque paramètre, copiez la « spécification de format » de ce paramètre "
 "à partir de l'argument de ``PyArg_Parse()`` et spécifiez *ça* comme "
@@ -577,7 +577,7 @@ msgstr ""
 
 #: howto/clinic.rst:336
 msgid ""
-"If the existing C function calls :c:func:`PyArg_ParseTuple` (as opposed to :"
+"If the existing C function calls :c:func:`PyArg_ParseTuple` (as opposed to :"
 "c:func:`PyArg_ParseTupleAndKeywords`), then all its arguments are positional-"
 "only."
 msgstr ""
@@ -671,7 +671,7 @@ msgstr ""
 #: howto/clinic.rst:424
 msgid ""
 "First, ensure both places use the same argument-parsing function. The "
-"existing code must call either :c:func:`PyArg_ParseTuple` or :c:func:"
+"existing code must call either :c:func:`PyArg_ParseTuple` or :c:func:"
 "`PyArg_ParseTupleAndKeywords`; ensure that the code generated by Argument "
 "Clinic calls the *exact* same function."
 msgstr ""
@@ -682,7 +682,7 @@ msgstr ""
 
 #: howto/clinic.rst:430
 msgid ""
-"Second, the format string passed in to :c:func:`PyArg_ParseTuple` or :c:func:"
+"Second, the format string passed in to :c:func:`PyArg_ParseTuple` or :c:func:"
 "`PyArg_ParseTupleAndKeywords` should be *exactly* the same as the hand-"
 "written one in the existing function, up to the colon or semi-colon."
 msgstr ""
@@ -717,7 +717,7 @@ msgstr ""
 #: howto/clinic.rst:445
 msgid ""
 "Fourth, inside the output portion of the block you'll find a preprocessor "
-"macro defining the appropriate static :c:type:`PyMethodDef` structure for "
+"macro defining the appropriate static :c:type:`PyMethodDef` structure for "
 "this builtin::"
 msgstr ""
 "Quatrièmement, à l'intérieur de la section sortie du bloc, vous trouverez "
@@ -726,7 +726,7 @@ msgstr ""
 
 #: howto/clinic.rst:452
 msgid ""
-"This static structure should be *exactly* the same as the existing static :c:"
+"This static structure should be *exactly* the same as the existing static :c:"
 "type:`PyMethodDef` structure for this builtin."
 msgstr ""
 "Cette structure statique doit être *exactement* la même que la structure "
@@ -781,8 +781,8 @@ msgstr ""
 
 #: howto/clinic.rst:522
 msgid ""
-"Remember the macro with the :c:type:`PyMethodDef` structure for this "
-"function?  Find the existing :c:type:`PyMethodDef` structure for this "
+"Remember the macro with the :c:type:`PyMethodDef` structure for this "
+"function?  Find the existing :c:type:`PyMethodDef` structure for this "
 "function and replace it with a reference to the macro.  (If the builtin is "
 "at module scope, this will probably be very near the end of the file; if the "
 "builtin is a class method, this will probably be below but relatively near "
@@ -798,7 +798,7 @@ msgstr ""
 #: howto/clinic.rst:529
 msgid ""
 "Note that the body of the macro contains a trailing comma.  So when you "
-"replace the existing static :c:type:`PyMethodDef` structure with the macro, "
+"replace the existing static :c:type:`PyMethodDef` structure with the macro, "
 "*don't* add a comma to the end."
 msgstr ""
 "Notez que le corps de la macro contient une virgule finale. Donc, lorsque "
@@ -963,7 +963,7 @@ msgstr "Conversion des fonctions en utilisant *PyArg_UnpackTuple*"
 
 #: howto/clinic.rst:623
 msgid ""
-"To convert a function parsing its arguments with :c:func:"
+"To convert a function parsing its arguments with :c:func:"
 "`PyArg_UnpackTuple`, simply write out all the arguments, specifying each as "
 "an ``object``.  You may specify the ``type`` argument to cast the type as "
 "appropriate.  All arguments should be marked positional-only (add a ``/`` on "
@@ -978,7 +978,7 @@ msgstr ""
 
 #: howto/clinic.rst:629
 msgid ""
-"Currently the generated code will use :c:func:`PyArg_ParseTuple`, but this "
+"Currently the generated code will use :c:func:`PyArg_ParseTuple`, but this "
 "will change soon."
 msgstr ""
 "Actuellement, le code généré utilise :c:func:`PyArg_ParseTuple`, mais cela "
@@ -992,10 +992,10 @@ msgstr "Groupes optionnels"
 msgid ""
 "Some legacy functions have a tricky approach to parsing their arguments: "
 "they count the number of positional arguments, then use a ``switch`` "
-"statement to call one of several different :c:func:`PyArg_ParseTuple` calls "
+"statement to call one of several different :c:func:`PyArg_ParseTuple` calls "
 "depending on how many positional arguments there are.  (These functions "
 "cannot accept keyword-only arguments.)  This approach was used to simulate "
-"optional arguments back before :c:func:`PyArg_ParseTupleAndKeywords` was "
+"optional arguments back before :c:func:`PyArg_ParseTupleAndKeywords` was "
 "created."
 msgstr ""
 "Certaines fonctions de base ont une approche particulière pour analyser "
@@ -1009,9 +1009,9 @@ msgstr ""
 
 #: howto/clinic.rst:642
 msgid ""
-"While functions using this approach can often be converted to use :c:func:"
+"While functions using this approach can often be converted to use :c:func:"
 "`PyArg_ParseTupleAndKeywords`, optional arguments, and default values, it's "
-"not always possible.  Some of these legacy functions have behaviors :c:func:"
+"not always possible.  Some of these legacy functions have behaviors :c:func:"
 "`PyArg_ParseTupleAndKeywords` doesn't directly support. The most obvious "
 "example is the builtin function ``range()``, which has an optional argument "
 "on the *left* side of its required argument! Another example is ``curses."
@@ -1053,7 +1053,7 @@ msgstr ""
 #: howto/clinic.rst:662
 msgid ""
 "Optional groups are *only* intended for use when converting functions that "
-"make multiple calls to :c:func:`PyArg_ParseTuple`! Functions that use *any* "
+"make multiple calls to :c:func:`PyArg_ParseTuple`! Functions that use *any* "
 "other approach for parsing arguments should *almost never* be converted to "
 "Argument Clinic using optional groups.  Functions using optional groups "
 "currently cannot have accurate signatures in Python, because Python just "
@@ -1186,7 +1186,7 @@ msgstr ""
 #: howto/clinic.rst:743
 msgid ""
 "In the future we may have a new argument parsing library that isn't "
-"restricted to what :c:func:`PyArg_ParseTuple` supports; this flexibility "
+"restricted to what :c:func:`PyArg_ParseTuple` supports; this flexibility "
 "won't be available to parameters using legacy converters."
 msgstr ""
 "Dans le futur, on pourrait avoir une nouvelle bibliothèque d'analyse des "
@@ -1230,7 +1230,7 @@ msgstr "``c_default``"
 msgid ""
 "The default value for this parameter when defined in C. Specifically, this "
 "will be the initializer for the variable declared in the \"parse function"
-"\".  See :ref:`the section on default values <default_values>` for how to "
+"\".  See :ref:`the section on default values <default_values>` for how to "
 "use this. Specified as a string."
 msgstr ""
 "La valeur par défaut de cet argument lorsqu'il est défini en C. Typiquement, "
@@ -1245,7 +1245,7 @@ msgstr "``annotation``"
 
 #: howto/clinic.rst:767
 msgid ""
-"The annotation value for this parameter.  Not currently supported, because :"
+"The annotation value for this parameter.  Not currently supported, because :"
 "pep:`8` mandates that the Python library may not use annotations."
 msgstr ""
 "La valeur annotée pour ce paramètre. Actuellement non géré, car la :pep:`8` "
@@ -1299,7 +1299,7 @@ msgstr "``converter``"
 
 #: howto/clinic.rst:788
 msgid ""
-"Only supported by the ``object`` converter.  Specifies the name of a :ref:`C "
+"Only supported by the ``object`` converter.  Specifies the name of a :ref:`C "
 "\"converter function\" <o_ampersand>` to use to convert this object to a "
 "native type."
 msgstr ""
@@ -1764,7 +1764,7 @@ msgstr "Py_buffer"
 #: howto/clinic.rst:895
 msgid ""
 "When using the ``Py_buffer`` converter (or the ``'s*'``, ``'w*'``, ``'*y'``, "
-"or ``'z*'`` legacy converters), you *must* not call :c:func:"
+"or ``'z*'`` legacy converters), you *must* not call :c:func:"
 "`PyBuffer_Release` on the provided buffer. Argument Clinic generates code "
 "that does it for you (in the parsing function)."
 msgstr ""
@@ -2197,7 +2197,7 @@ msgid ""
 "converters! A converter is simply a Python class that inherits from "
 "``CConverter``. The main purpose of a custom converter is if you have a "
 "parameter using the ``O&`` format unit—parsing this parameter means calling "
-"a :c:func:`PyArg_ParseTuple` \"converter function\"."
+"a :c:func:`PyArg_ParseTuple` \"converter function\"."
 msgstr ""
 
 #: howto/clinic.rst:1219
@@ -2293,7 +2293,7 @@ msgstr ""
 #: howto/clinic.rst:1274
 msgid ""
 "A boolean value.  If true, Argument Clinic will add a ``&`` in front of the "
-"name of the variable when passing it into :c:func:`PyArg_ParseTuple`."
+"name of the variable when passing it into :c:func:`PyArg_ParseTuple`."
 msgstr ""
 
 #: howto/clinic.rst:1279
@@ -2558,9 +2558,9 @@ msgstr ""
 msgid ""
 "``output push`` and ``output pop`` allow you to push and pop configurations "
 "on an internal configuration stack, so that you can temporarily modify the "
-"output configuration, then easily restore the previous configuration. Simply "
-"push before your change to save the current configuration, then pop when you "
-"wish to restore the previous configuration."
+"output configuration, then easily restore the previous configuration.  "
+"Simply push before your change to save the current configuration, then pop "
+"when you wish to restore the previous configuration."
 msgstr ""
 
 #: howto/clinic.rst:1478