msgmerge 3.7
This commit is contained in:
parent fe4f5fa729
commit aed24996a1
209 changed files with 29092 additions and 18207 deletions
| | @ -7,7 +7,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2018-06-10 11:27+0200\n" | ||||
"POT-Creation-Date: 2018-06-28 15:29+0200\n" | ||||
"PO-Revision-Date: 2018-06-17 11:04+0200\n" | ||||
"Last-Translator: Julien Palard <julien@palard.fr>\n" | ||||
"Language-Team: \n" | ||||
| | @ -1804,8 +1804,8 @@ msgstr "" | |||
#: ../Doc/howto/clinic.rst:1066 | ||||
msgid "" | ||||
"None of these take parameters. For the first three, return -1 to indicate " | ||||
"error. For ``DecodeFSDefault``, the return type is ``char *``; return a " | ||||
"NULL pointer to indicate an error." | ||||
"error. For ``DecodeFSDefault``, the return type is ``const char *``; return " | ||||
"a NULL pointer to indicate an error." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/clinic.rst:1070 | ||||
| | | |||
| | @ -8,7 +8,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2018-06-10 11:27+0200\n" | ||||
"POT-Creation-Date: 2018-06-28 15:29+0200\n" | ||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" | ||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" | ||||
"Language-Team: LANGUAGE <LL@li.org>\n" | ||||
| | @ -717,7 +717,7 @@ msgid "" | |||
msgstr "" | ||||
| ||||
#: ../Doc/howto/curses.rst:546 | ||||
msgid "`The ncurses man page <http://linux.die.net/man/3/ncurses>`_" | ||||
msgid "`The ncurses man page <https://linux.die.net/man/3/ncurses>`_" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/curses.rst:547 | ||||
| | | |||
| | @ -8,7 +8,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2018-04-29 00:24+0200\n" | ||||
"POT-Creation-Date: 2018-06-28 15:29+0200\n" | ||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" | ||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" | ||||
"Language-Team: LANGUAGE <LL@li.org>\n" | ||||
| | @ -261,33 +261,45 @@ msgid "" | |||
msgstr "" | ||||
| ||||
#: ../Doc/howto/instrumentation.rst:321 | ||||
msgid "" | ||||
"Fires before :mod:`importlib` attempts to find and load the module. ``arg0`` " | ||||
"is the module name." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/instrumentation.rst:328 | ||||
msgid "" | ||||
"Fires after :mod:`importlib`'s find_and_load function is called. ``arg0`` is " | ||||
"the module name, ``arg1`` indicates if module was successfully loaded." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/instrumentation.rst:336 | ||||
msgid "SystemTap Tapsets" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/instrumentation.rst:323 | ||||
#: ../Doc/howto/instrumentation.rst:338 | ||||
msgid "" | ||||
"The higher-level way to use the SystemTap integration is to use a \"tapset" | ||||
"\": SystemTap's equivalent of a library, which hides some of the lower-level " | ||||
"details of the static markers." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/instrumentation.rst:327 | ||||
#: ../Doc/howto/instrumentation.rst:342 | ||||
msgid "Here is a tapset file, based on a non-shared build of CPython:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/instrumentation.rst:350 | ||||
#: ../Doc/howto/instrumentation.rst:365 | ||||
msgid "" | ||||
"If this file is installed in SystemTap's tapset directory (e.g. ``/usr/share/" | ||||
"systemtap/tapset``), then these additional probepoints become available:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/instrumentation.rst:356 | ||||
#: ../Doc/howto/instrumentation.rst:371 | ||||
msgid "" | ||||
"This probe point indicates that execution of a Python function has begun. It " | ||||
"is only triggered for pure-python (bytecode) functions." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/instrumentation.rst:361 | ||||
#: ../Doc/howto/instrumentation.rst:376 | ||||
msgid "" | ||||
"This probe point is the converse of :c:func:`python.function.return`, and " | ||||
"indicates that execution of a Python function has ended (either via " | ||||
| | @ -295,18 +307,18 @@ msgid "" | |||
"(bytecode) functions." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/instrumentation.rst:368 | ||||
#: ../Doc/howto/instrumentation.rst:383 | ||||
msgid "Examples" | ||||
msgstr "Exemples" | ||||
| ||||
#: ../Doc/howto/instrumentation.rst:369 | ||||
#: ../Doc/howto/instrumentation.rst:384 | ||||
msgid "" | ||||
"This SystemTap script uses the tapset above to more cleanly implement the " | ||||
"example given above of tracing the Python function-call hierarchy, without " | ||||
"needing to directly name the static markers:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/instrumentation.rst:388 | ||||
#: ../Doc/howto/instrumentation.rst:403 | ||||
msgid "" | ||||
"The following script uses the tapset above to provide a top-like view of all " | ||||
"running CPython code, showing the top 20 most frequently-entered bytecode " | ||||
| | | |||
| | @ -8,7 +8,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2018-06-10 11:27+0200\n" | ||||
"POT-Creation-Date: 2018-06-28 15:29+0200\n" | ||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" | ||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" | ||||
"Language-Team: LANGUAGE <LL@li.org>\n" | ||||
| | @ -533,7 +533,7 @@ msgid "" | |||
"you cannot directly make logging calls using :meth:`str.format` or :class:" | ||||
"`string.Template` syntax, because internally the logging package uses %-" | ||||
"formatting to merge the format string and the variable arguments. There " | ||||
"would no changing this while preserving backward compatibility, since all " | ||||
"would be no changing this while preserving backward compatibility, since all " | ||||
"logging calls which are out there in existing code will be using %-format " | ||||
"strings." | ||||
msgstr "" | ||||
| | | |||
| | @ -8,7 +8,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2018-06-10 11:27+0200\n" | ||||
"POT-Creation-Date: 2018-06-28 15:29+0200\n" | ||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" | ||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" | ||||
"Language-Team: LANGUAGE <LL@li.org>\n" | ||||
| | @ -407,8 +407,8 @@ msgid "" | |||
"If your logging needs are simple, then use the above examples to incorporate " | ||||
"logging into your own scripts, and if you run into problems or don't " | ||||
"understand something, please post a question on the comp.lang.python Usenet " | ||||
"group (available at https://groups.google.com/group/comp.lang.python) and " | ||||
"you should receive help before too long." | ||||
"group (available at https://groups.google.com/forum/#!forum/comp.lang." | ||||
"python) and you should receive help before too long." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/logging.rst:332 | ||||
| | | |||
234 howto/regex.po
234
howto/regex.po | | @ -7,7 +7,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2018-02-08 09:58+0100\n" | ||||
"POT-Creation-Date: 2018-06-28 15:29+0200\n" | ||||
"PO-Revision-Date: 2018-06-17 11:06+0200\n" | ||||
"Last-Translator: Nabil Bendafi <nabil@bendafi.fr>\n" | ||||
"Language-Team: \n" | ||||
| | @ -752,12 +752,12 @@ msgstr "" | |||
"documentation :mod:`re` pour la liste complète." | ||||
| ||||
#: ../Doc/howto/regex.rst:359 ../Doc/howto/regex.rst:417 | ||||
#: ../Doc/howto/regex.rst:1054 | ||||
#: ../Doc/howto/regex.rst:1056 | ||||
msgid "Method/Attribute" | ||||
msgstr "Méthode/Attribut" | ||||
| ||||
#: ../Doc/howto/regex.rst:359 ../Doc/howto/regex.rst:417 | ||||
#: ../Doc/howto/regex.rst:1054 | ||||
#: ../Doc/howto/regex.rst:1056 | ||||
msgid "Purpose" | ||||
msgstr "Objectif" | ||||
| ||||
| | @ -797,7 +797,7 @@ msgstr "" | |||
| ||||
#: ../Doc/howto/regex.rst:374 | ||||
msgid "" | ||||
":meth:`~re.pattern.match` and :meth:`~re.pattern.search` return ``None`` if " | ||||
":meth:`~re.Pattern.match` and :meth:`~re.Pattern.search` return ``None`` if " | ||||
"no match can be found. If they're successful, a :ref:`match object <match-" | ||||
"objects>` instance is returned, containing information about the match: " | ||||
"where it starts and ends, the substring it matched, and more." | ||||
| | @ -823,7 +823,7 @@ msgstr "" | |||
msgid "" | ||||
"Now, you can try matching various strings against the RE ``[a-z]+``. An " | ||||
"empty string shouldn't match at all, since ``+`` means 'one or more " | ||||
"repetitions'. :meth:`~re.pattern.match` should return ``None`` in this case, " | ||||
"repetitions'. :meth:`~re.Pattern.match` should return ``None`` in this case, " | ||||
"which will cause the interpreter to print no output. You can explicitly " | ||||
"print the result of :meth:`!match` to make this clear. ::" | ||||
msgstr "" | ||||
| | @ -831,7 +831,7 @@ msgstr "" | |||
#: ../Doc/howto/regex.rst:404 | ||||
msgid "" | ||||
"Now, let's try it on a string that it should match, such as ``tempo``. In " | ||||
"this case, :meth:`~re.pattern.match` will return a :ref:`match object <match-" | ||||
"this case, :meth:`~re.Pattern.match` will return a :ref:`match object <match-" | ||||
"objects>`, so you should store the result in a variable for later use. ::" | ||||
msgstr "" | ||||
| ||||
| | @ -880,12 +880,12 @@ msgstr "" | |||
| ||||
#: ../Doc/howto/regex.rst:438 | ||||
msgid "" | ||||
":meth:`~re.match.group` returns the substring that was matched by the RE. :" | ||||
"meth:`~re.match.start` and :meth:`~re.match.end` return the starting and " | ||||
"ending index of the match. :meth:`~re.match.span` returns both start and end " | ||||
"indexes in a single tuple. Since the :meth:`~re.pattern.match` method only " | ||||
":meth:`~re.Match.group` returns the substring that was matched by the RE. :" | ||||
"meth:`~re.Match.start` and :meth:`~re.Match.end` return the starting and " | ||||
"ending index of the match. :meth:`~re.Match.span` returns both start and end " | ||||
"indexes in a single tuple. Since the :meth:`~re.Pattern.match` method only " | ||||
"checks if the RE matches at the start of a string, :meth:`!start` will " | ||||
"always be zero. However, the :meth:`~re.pattern.search` method of patterns " | ||||
"always be zero. However, the :meth:`~re.Pattern.search` method of patterns " | ||||
"scans through the string, so the match may not start at zero in that " | ||||
"case. ::" | ||||
msgstr "" | ||||
| | @ -900,7 +900,7 @@ msgstr "" | |||
#: ../Doc/howto/regex.rst:466 | ||||
msgid "" | ||||
"Two pattern methods return all of the matches for a pattern. :meth:`~re." | ||||
"pattern.findall` returns a list of matching strings::" | ||||
"Pattern.findall` returns a list of matching strings::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:473 | ||||
| | @ -1309,17 +1309,17 @@ msgid "" | |||
"matched or not. Regular expressions are often used to dissect strings by " | ||||
"writing a RE divided into several subgroups which match different components " | ||||
"of interest. For example, an RFC-822 header line is divided into a header " | ||||
"name and a value, separated by a ``':'``, like this::" | ||||
"name and a value, separated by a ``':'``, like this:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:796 | ||||
#: ../Doc/howto/regex.rst:798 | ||||
msgid "" | ||||
"This can be handled by writing a regular expression which matches an entire " | ||||
"header line, and has one group which matches the header name, and another " | ||||
"group which matches the header's value." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:800 | ||||
#: ../Doc/howto/regex.rst:802 | ||||
msgid "" | ||||
"Groups are marked by the ``'('``, ``')'`` metacharacters. ``'('`` and " | ||||
"``')'`` have much the same meaning as they do in mathematical expressions; " | ||||
| | @ -1329,39 +1329,39 @@ msgid "" | |||
"repetitions of ``ab``. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:811 | ||||
#: ../Doc/howto/regex.rst:813 | ||||
msgid "" | ||||
"Groups indicated with ``'('``, ``')'`` also capture the starting and ending " | ||||
"index of the text that they match; this can be retrieved by passing an " | ||||
"argument to :meth:`~re.match.group`, :meth:`~re.match.start`, :meth:`~re." | ||||
"match.end`, and :meth:`~re.match.span`. Groups are numbered starting with " | ||||
"argument to :meth:`~re.Match.group`, :meth:`~re.Match.start`, :meth:`~re." | ||||
"Match.end`, and :meth:`~re.Match.span`. Groups are numbered starting with " | ||||
"0. Group 0 is always present; it's the whole RE, so :ref:`match object " | ||||
"<match-objects>` methods all have group 0 as their default argument. Later " | ||||
"we'll see how to express groups that don't capture the span of text that " | ||||
"they match. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:827 | ||||
#: ../Doc/howto/regex.rst:829 | ||||
msgid "" | ||||
"Subgroups are numbered from left to right, from 1 upward. Groups can be " | ||||
"nested; to determine the number, just count the opening parenthesis " | ||||
"characters, going from left to right. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:840 | ||||
#: ../Doc/howto/regex.rst:842 | ||||
msgid "" | ||||
":meth:`~re.match.group` can be passed multiple group numbers at a time, in " | ||||
":meth:`~re.Match.group` can be passed multiple group numbers at a time, in " | ||||
"which case it will return a tuple containing the corresponding values for " | ||||
"those groups. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:846 | ||||
#: ../Doc/howto/regex.rst:848 | ||||
msgid "" | ||||
"The :meth:`~re.match.groups` method returns a tuple containing the strings " | ||||
"The :meth:`~re.Match.groups` method returns a tuple containing the strings " | ||||
"for all the subgroups, from 1 up to however many there are. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:852 | ||||
#: ../Doc/howto/regex.rst:854 | ||||
msgid "" | ||||
"Backreferences in a pattern allow you to specify that the contents of an " | ||||
"earlier capturing group must also be found at the current location in the " | ||||
| | @ -1372,11 +1372,11 @@ msgid "" | |||
"when incorporating backreferences in a RE." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:860 | ||||
#: ../Doc/howto/regex.rst:862 | ||||
msgid "For example, the following RE detects doubled words in a string. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:866 | ||||
#: ../Doc/howto/regex.rst:868 | ||||
msgid "" | ||||
"Backreferences like this aren't often useful for just searching through a " | ||||
"string --- there are few text formats which repeat data in this way --- but " | ||||
| | @ -1384,11 +1384,11 @@ msgid "" | |||
"substitutions." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:872 | ||||
#: ../Doc/howto/regex.rst:874 | ||||
msgid "Non-capturing and Named Groups" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:874 | ||||
#: ../Doc/howto/regex.rst:876 | ||||
msgid "" | ||||
"Elaborate REs may use many groups, both to capture substrings of interest, " | ||||
"and to group and structure the RE itself. In complex REs, it becomes " | ||||
| | @ -1397,7 +1397,7 @@ msgid "" | |||
"expression extensions, so we'll look at that first." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:880 | ||||
#: ../Doc/howto/regex.rst:882 | ||||
msgid "" | ||||
"Perl 5 is well known for its powerful additions to standard regular " | ||||
"expressions. For these new features the Perl developers couldn't choose new " | ||||
| | @ -1408,7 +1408,7 @@ msgid "" | |||
"wouldn't have escaped it by writing ``\\&`` or ``[&]``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:887 | ||||
#: ../Doc/howto/regex.rst:889 | ||||
msgid "" | ||||
"The solution chosen by the Perl developers was to use ``(?...)`` as the " | ||||
"extension syntax. ``?`` immediately after a parenthesis was a syntax error " | ||||
| | @ -1419,20 +1419,20 @@ msgid "" | |||
"capturing group containing the subexpression ``foo``)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:895 | ||||
#: ../Doc/howto/regex.rst:897 | ||||
msgid "" | ||||
"Python supports several of Perl's extensions and adds an extension syntax to " | ||||
"Perl's extension syntax. If the first character after the question mark is " | ||||
"a ``P``, you know that it's an extension that's specific to Python." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:900 | ||||
#: ../Doc/howto/regex.rst:902 | ||||
msgid "" | ||||
"Now that we've looked at the general extension syntax, we can return to the " | ||||
"features that simplify working with groups in complex REs." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:903 | ||||
#: ../Doc/howto/regex.rst:905 | ||||
msgid "" | ||||
"Sometimes you'll want to use a group to denote a part of a regular " | ||||
"expression, but aren't interested in retrieving the group's contents. You " | ||||
| | @ -1440,7 +1440,7 @@ msgid "" | |||
"where you can replace the ``...`` with any other regular expression. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:915 | ||||
#: ../Doc/howto/regex.rst:917 | ||||
msgid "" | ||||
"Except for the fact that you can't retrieve the contents of what the group " | ||||
"matched, a non-capturing group behaves exactly the same as a capturing " | ||||
| | @ -1453,13 +1453,13 @@ msgid "" | |||
"groups; neither form is any faster than the other." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:924 | ||||
#: ../Doc/howto/regex.rst:926 | ||||
msgid "" | ||||
"A more significant feature is named groups: instead of referring to them by " | ||||
"numbers, groups can be referenced by a name." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:927 | ||||
#: ../Doc/howto/regex.rst:929 | ||||
msgid "" | ||||
"The syntax for a named group is one of the Python-specific extensions: ``(?" | ||||
"P<name>...)``. *name* is, obviously, the name of the group. Named groups " | ||||
| | @ -1471,20 +1471,20 @@ msgid "" | |||
"ways::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:942 | ||||
#: ../Doc/howto/regex.rst:944 | ||||
msgid "" | ||||
"Named groups are handy because they let you use easily-remembered names, " | ||||
"instead of having to remember numbers. Here's an example RE from the :mod:" | ||||
"`imaplib` module::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:953 | ||||
#: ../Doc/howto/regex.rst:955 | ||||
msgid "" | ||||
"It's obviously much easier to retrieve ``m.group('zonem')``, instead of " | ||||
"having to remember to retrieve group 9." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:956 | ||||
#: ../Doc/howto/regex.rst:958 | ||||
msgid "" | ||||
"The syntax for backreferences in an expression such as ``(...)\\1`` refers " | ||||
"to the number of the group. There's naturally a variant that uses the group " | ||||
| | @ -1495,22 +1495,22 @@ msgid "" | |||
"+(?P=word)\\b``::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:969 | ||||
#: ../Doc/howto/regex.rst:971 | ||||
msgid "Lookahead Assertions" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:971 | ||||
#: ../Doc/howto/regex.rst:973 | ||||
msgid "" | ||||
"Another zero-width assertion is the lookahead assertion. Lookahead " | ||||
"assertions are available in both positive and negative form, and look like " | ||||
"this:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:979 | ||||
#: ../Doc/howto/regex.rst:981 | ||||
msgid "``(?=...)``" | ||||
msgstr "``(?=...)``" | ||||
| ||||
#: ../Doc/howto/regex.rst:975 | ||||
#: ../Doc/howto/regex.rst:977 | ||||
msgid "" | ||||
"Positive lookahead assertion. This succeeds if the contained regular " | ||||
"expression, represented here by ``...``, successfully matches at the current " | ||||
| | @ -1519,18 +1519,18 @@ msgid "" | |||
"is tried right where the assertion started." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:984 | ||||
#: ../Doc/howto/regex.rst:986 | ||||
msgid "``(?!...)``" | ||||
msgstr "``(?!...)``" | ||||
| ||||
#: ../Doc/howto/regex.rst:982 | ||||
#: ../Doc/howto/regex.rst:984 | ||||
msgid "" | ||||
"Negative lookahead assertion. This is the opposite of the positive " | ||||
"assertion; it succeeds if the contained expression *doesn't* match at the " | ||||
"current position in the string." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:986 | ||||
#: ../Doc/howto/regex.rst:988 | ||||
msgid "" | ||||
"To make this concrete, let's look at a case where a lookahead is useful. " | ||||
"Consider a simple pattern to match a filename and split it apart into a base " | ||||
| | @ -1538,15 +1538,15 @@ msgid "" | |||
"``news`` is the base name, and ``rc`` is the filename's extension." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:991 | ||||
#: ../Doc/howto/regex.rst:993 | ||||
msgid "The pattern to match this is quite simple:" | ||||
msgstr "Le motif de correspondance est plutôt simple: " | ||||
| ||||
#: ../Doc/howto/regex.rst:993 | ||||
#: ../Doc/howto/regex.rst:995 | ||||
msgid "``.*[.].*$``" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:995 | ||||
#: ../Doc/howto/regex.rst:997 | ||||
msgid "" | ||||
"Notice that the ``.`` needs to be treated specially because it's a " | ||||
"metacharacter, so it's inside a character class to only match that specific " | ||||
| | @ -1556,24 +1556,24 @@ msgid "" | |||
"``printers.conf``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1002 | ||||
#: ../Doc/howto/regex.rst:1004 | ||||
msgid "" | ||||
"Now, consider complicating the problem a bit; what if you want to match " | ||||
"filenames where the extension is not ``bat``? Some incorrect attempts:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1005 | ||||
#: ../Doc/howto/regex.rst:1007 | ||||
msgid "" | ||||
"``.*[.][^b].*$`` The first attempt above tries to exclude ``bat`` by " | ||||
"requiring that the first character of the extension is not a ``b``. This is " | ||||
"wrong, because the pattern also doesn't match ``foo.bar``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1009 | ||||
#: ../Doc/howto/regex.rst:1011 | ||||
msgid "``.*[.]([^b]..|.[^a].|..[^t])$``" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1011 | ||||
#: ../Doc/howto/regex.rst:1013 | ||||
msgid "" | ||||
"The expression gets messier when you try to patch up the first solution by " | ||||
"requiring one of the following cases to match: the first character of the " | ||||
| | @ -1584,18 +1584,18 @@ msgid "" | |||
"pattern again in an effort to fix it." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1019 | ||||
#: ../Doc/howto/regex.rst:1021 | ||||
msgid "``.*[.]([^b].?.?|.[^a]?.?|..?[^t]?)$``" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1021 | ||||
#: ../Doc/howto/regex.rst:1023 | ||||
msgid "" | ||||
"In the third attempt, the second and third letters are all made optional in " | ||||
"order to allow matching extensions shorter than three characters, such as " | ||||
"``sendmail.cf``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1025 | ||||
#: ../Doc/howto/regex.rst:1027 | ||||
msgid "" | ||||
"The pattern's getting really complicated now, which makes it hard to read " | ||||
"and understand. Worse, if the problem changes and you want to exclude both " | ||||
| | @ -1603,11 +1603,11 @@ msgid "" | |||
"complicated and confusing." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1030 | ||||
#: ../Doc/howto/regex.rst:1032 | ||||
msgid "A negative lookahead cuts through all this confusion:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1032 | ||||
#: ../Doc/howto/regex.rst:1034 | ||||
msgid "" | ||||
"``.*[.](?!bat$)[^.]*$`` The negative lookahead means: if the expression " | ||||
"``bat`` doesn't match at this point, try the rest of the pattern; if ``bat" | ||||
| | @ -1617,43 +1617,43 @@ msgid "" | |||
"pattern works when there are multiple dots in the filename." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1039 | ||||
#: ../Doc/howto/regex.rst:1041 | ||||
msgid "" | ||||
"Excluding another filename extension is now easy; simply add it as an " | ||||
"alternative inside the assertion. The following pattern excludes filenames " | ||||
"that end in either ``bat`` or ``exe``:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1043 | ||||
#: ../Doc/howto/regex.rst:1045 | ||||
msgid "``.*[.](?!bat$|exe$)[^.]*$``" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1047 | ||||
#: ../Doc/howto/regex.rst:1049 | ||||
msgid "Modifying Strings" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1049 | ||||
#: ../Doc/howto/regex.rst:1051 | ||||
msgid "" | ||||
"Up to this point, we've simply performed searches against a static string. " | ||||
"Regular expressions are also commonly used to modify strings in various " | ||||
"ways, using the following pattern methods:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1056 | ||||
#: ../Doc/howto/regex.rst:1058 | ||||
msgid "``split()``" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1056 | ||||
#: ../Doc/howto/regex.rst:1058 | ||||
msgid "Split the string into a list, splitting it wherever the RE matches" | ||||
msgstr "" | ||||
"Découpe la chaîne de caractère en liste, la découpant partout où la RE " | ||||
"correspond" | ||||
| ||||
#: ../Doc/howto/regex.rst:1059 | ||||
#: ../Doc/howto/regex.rst:1061 | ||||
msgid "``sub()``" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1059 | ||||
#: ../Doc/howto/regex.rst:1061 | ||||
msgid "" | ||||
"Find all substrings where the RE matches, and replace them with a different " | ||||
"string" | ||||
| | @ -1661,23 +1661,23 @@ msgstr "" | |||
"Rechercher toutes les sous-chaînes de caractères où correspond la RE et les " | ||||
"substituer par une chaîne de caractères différente " | ||||
| ||||
#: ../Doc/howto/regex.rst:1062 | ||||
#: ../Doc/howto/regex.rst:1064 | ||||
msgid "``subn()``" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1062 | ||||
#: ../Doc/howto/regex.rst:1064 | ||||
msgid "" | ||||
"Does the same thing as :meth:`!sub`, but returns the new string and the " | ||||
"number of replacements" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1069 | ||||
#: ../Doc/howto/regex.rst:1071 | ||||
msgid "Splitting Strings" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1071 | ||||
#: ../Doc/howto/regex.rst:1073 | ||||
msgid "" | ||||
"The :meth:`~re.pattern.split` method of a pattern splits a string apart " | ||||
"The :meth:`~re.Pattern.split` method of a pattern splits a string apart " | ||||
"wherever the RE matches, returning a list of the pieces. It's similar to " | ||||
"the :meth:`~str.split` method of strings but provides much more generality " | ||||
"in the delimiters that you can split by; string :meth:`!split` only supports " | ||||
| | @ -1685,7 +1685,7 @@ msgid "" | |||
"module-level :func:`re.split` function, too." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1082 | ||||
#: ../Doc/howto/regex.rst:1084 | ||||
msgid "" | ||||
"Split *string* by the matches of the regular expression. If capturing " | ||||
"parentheses are used in the RE, then their contents will also be returned as " | ||||
| | @ -1693,7 +1693,7 @@ msgid "" | |||
"splits are performed." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1087 | ||||
#: ../Doc/howto/regex.rst:1089 | ||||
msgid "" | ||||
"You can limit the number of splits made, by passing a value for *maxsplit*. " | ||||
"When *maxsplit* is nonzero, at most *maxsplit* splits will be made, and the " | ||||
| | @ -1702,7 +1702,7 @@ msgid "" | |||
"characters. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1099 | ||||
#: ../Doc/howto/regex.rst:1101 | ||||
msgid "" | ||||
"Sometimes you're not only interested in what the text between delimiters is, " | ||||
"but also need to know what the delimiter was. If capturing parentheses are " | ||||
| | @ -1710,58 +1710,58 @@ msgid "" | |||
"Compare the following calls::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1111 | ||||
#: ../Doc/howto/regex.rst:1113 | ||||
msgid "" | ||||
"The module-level function :func:`re.split` adds the RE to be used as the " | ||||
"first argument, but is otherwise the same. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1123 | ||||
#: ../Doc/howto/regex.rst:1125 | ||||
msgid "Search and Replace" | ||||
msgstr "Recherche et Substitution" | ||||
| ||||
#: ../Doc/howto/regex.rst:1125 | ||||
#: ../Doc/howto/regex.rst:1127 | ||||
msgid "" | ||||
"Another common task is to find all the matches for a pattern, and replace " | ||||
"them with a different string. The :meth:`~re.pattern.sub` method takes a " | ||||
"them with a different string. The :meth:`~re.Pattern.sub` method takes a " | ||||
"replacement value, which can be either a string or a function, and the " | ||||
"string to be processed." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1132 | ||||
#: ../Doc/howto/regex.rst:1134 | ||||
msgid "" | ||||
"Returns the string obtained by replacing the leftmost non-overlapping " | ||||
"occurrences of the RE in *string* by the replacement *replacement*. If the " | ||||
"pattern isn't found, *string* is returned unchanged." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1136 | ||||
#: ../Doc/howto/regex.rst:1138 | ||||
msgid "" | ||||
"The optional argument *count* is the maximum number of pattern occurrences " | ||||
"to be replaced; *count* must be a non-negative integer. The default value " | ||||
"of 0 means to replace all occurrences." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1140 | ||||
#: ../Doc/howto/regex.rst:1142 | ||||
msgid "" | ||||
"Here's a simple example of using the :meth:`~re.pattern.sub` method. It " | ||||
"Here's a simple example of using the :meth:`~re.Pattern.sub` method. It " | ||||
"replaces colour names with the word ``colour``::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1149 | ||||
#: ../Doc/howto/regex.rst:1151 | ||||
msgid "" | ||||
"The :meth:`~re.pattern.subn` method does the same work, but returns a 2-" | ||||
"The :meth:`~re.Pattern.subn` method does the same work, but returns a 2-" | ||||
"tuple containing the new string value and the number of replacements that " | ||||
"were performed::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1158 | ||||
#: ../Doc/howto/regex.rst:1160 | ||||
msgid "" | ||||
"Empty matches are replaced only when they're not adjacent to a previous " | ||||
"match. ::" | ||||
"empty match. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1165 | ||||
#: ../Doc/howto/regex.rst:1167 | ||||
msgid "" | ||||
"If *replacement* is a string, any backslash escapes in it are processed. " | ||||
"That is, ``\\n`` is converted to a single newline character, ``\\r`` is " | ||||
| | @ -1772,13 +1772,13 @@ msgid "" | |||
"string." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1172 | ||||
#: ../Doc/howto/regex.rst:1174 | ||||
msgid "" | ||||
"This example matches the word ``section`` followed by a string enclosed in " | ||||
"``{``, ``}``, and changes ``section`` to ``subsection``::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1179 | ||||
#: ../Doc/howto/regex.rst:1181 | ||||
msgid "" | ||||
"There's also a syntax for referring to named groups as defined by the ``(?" | ||||
"P<name>...)`` syntax. ``\\g<name>`` will use the substring matched by the " | ||||
| | @ -1790,7 +1790,7 @@ msgid "" | |||
"but use all three variations of the replacement string. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1196 | ||||
#: ../Doc/howto/regex.rst:1198 | ||||
msgid "" | ||||
"*replacement* can also be a function, which gives you even more control. If " | ||||
"*replacement* is a function, the function is called for every non-" | ||||
| | @ -1799,13 +1799,13 @@ msgid "" | |||
"this information to compute the desired replacement string and return it." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1202 | ||||
#: ../Doc/howto/regex.rst:1204 | ||||
msgid "" | ||||
"In the following example, the replacement function translates decimals into " | ||||
"hexadecimal::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1214 | ||||
#: ../Doc/howto/regex.rst:1216 | ||||
msgid "" | ||||
"When using the module-level :func:`re.sub` function, the pattern is passed " | ||||
"as the first argument. The pattern may be provided as an object or as a " | ||||
| | @ -1815,11 +1815,11 @@ msgid "" | |||
"x'``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1222 | ||||
#: ../Doc/howto/regex.rst:1224 | ||||
msgid "Common Problems" | ||||
msgstr "Problèmes courants" | ||||
| ||||
#: ../Doc/howto/regex.rst:1224 | ||||
#: ../Doc/howto/regex.rst:1226 | ||||
msgid "" | ||||
"Regular expressions are a powerful tool for some applications, but in some " | ||||
"ways their behaviour isn't intuitive and at times they don't behave the way " | ||||
| | @ -1827,11 +1827,11 @@ msgid "" | |||
"pitfalls." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1230 | ||||
#: ../Doc/howto/regex.rst:1232 | ||||
msgid "Use String Methods" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1232 | ||||
#: ../Doc/howto/regex.rst:1234 | ||||
msgid "" | ||||
"Sometimes using the :mod:`re` module is a mistake. If you're matching a " | ||||
"fixed string, or a single character class, and you're not using any :mod:" | ||||
| | @ -1843,7 +1843,7 @@ msgid "" | |||
"engine." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1240 | ||||
#: ../Doc/howto/regex.rst:1242 | ||||
msgid "" | ||||
"One example might be replacing a single fixed string with another one; for " | ||||
"example, you might replace ``word`` with ``deed``. :func:`re.sub` seems " | ||||
| | @ -1856,7 +1856,7 @@ msgid "" | |||
"meth:`!replace`'s abilities.)" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1249 | ||||
#: ../Doc/howto/regex.rst:1251 | ||||
msgid "" | ||||
"Another common task is deleting every occurrence of a single character from " | ||||
"a string or replacing it with another single character. You might do this " | ||||
| | @ -1865,17 +1865,17 @@ msgid "" | |||
"operation can be." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1255 | ||||
#: ../Doc/howto/regex.rst:1257 | ||||
msgid "" | ||||
"In short, before turning to the :mod:`re` module, consider whether your " | ||||
"problem can be solved with a faster and simpler string method." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1260 | ||||
#: ../Doc/howto/regex.rst:1262 | ||||
msgid "match() versus search()" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1262 | ||||
#: ../Doc/howto/regex.rst:1264 | ||||
msgid "" | ||||
"The :func:`~re.match` function only checks if the RE matches at the " | ||||
"beginning of the string while :func:`~re.search` will scan forward through " | ||||
| | @ -1885,13 +1885,13 @@ msgid "" | |||
"report it. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1273 | ||||
#: ../Doc/howto/regex.rst:1275 | ||||
msgid "" | ||||
"On the other hand, :func:`~re.search` will scan forward through the string, " | ||||
"reporting the first match it finds. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1281 | ||||
#: ../Doc/howto/regex.rst:1283 | ||||
msgid "" | ||||
"Sometimes you'll be tempted to keep using :func:`re.match`, and just add ``." | ||||
"*`` to the front of your RE. Resist this temptation and use :func:`re." | ||||
| | @ -1903,18 +1903,18 @@ msgid "" | |||
"starting character, only trying the full match if a ``'C'`` is found." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1290 | ||||
#: ../Doc/howto/regex.rst:1292 | ||||
msgid "" | ||||
"Adding ``.*`` defeats this optimization, requiring scanning to the end of " | ||||
"the string and then backtracking to find a match for the rest of the RE. " | ||||
"Use :func:`re.search` instead." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1296 | ||||
#: ../Doc/howto/regex.rst:1298 | ||||
msgid "Greedy versus Non-Greedy" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1298 | ||||
#: ../Doc/howto/regex.rst:1300 | ||||
msgid "" | ||||
"When repeating a regular expression, as in ``a*``, the resulting action is " | ||||
"to consume as much of the pattern as possible. This fact often bites you " | ||||
| | @ -1923,7 +1923,7 @@ msgid "" | |||
"HTML tag doesn't work because of the greedy nature of ``.*``. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1312 | ||||
#: ../Doc/howto/regex.rst:1314 | ||||
msgid "" | ||||
"The RE matches the ``'<'`` in ``'<html>'``, and the ``.*`` consumes the rest " | ||||
"of the string. There's still more left in the RE, though, and the ``>`` " | ||||
| | @ -1933,7 +1933,7 @@ msgid "" | |||
"``'</title>'``, which isn't what you want." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1319 | ||||
#: ../Doc/howto/regex.rst:1321 | ||||
msgid "" | ||||
"In this case, the solution is to use the non-greedy qualifiers ``*?``, ``+?" | ||||
"``, ``??``, or ``{m,n}?``, which match as *little* text as possible. In the " | ||||
| | @ -1942,7 +1942,7 @@ msgid "" | |||
"retrying the ``'>'`` at every step. This produces just the right result::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1328 | ||||
#: ../Doc/howto/regex.rst:1330 | ||||
msgid "" | ||||
"(Note that parsing HTML or XML with regular expressions is painful. Quick-" | ||||
"and-dirty patterns will handle common cases, but HTML and XML have special " | ||||
| | @ -1952,11 +1952,11 @@ msgid "" | |||
"such tasks.)" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1336 | ||||
#: ../Doc/howto/regex.rst:1338 | ||||
msgid "Using re.VERBOSE" | ||||
msgstr "Utilisez re.VERBOSE" | ||||
| ||||
#: ../Doc/howto/regex.rst:1338 | ||||
#: ../Doc/howto/regex.rst:1340 | ||||
msgid "" | ||||
"By now you've probably noticed that regular expressions are a very compact " | ||||
"notation, but they're not terribly readable. REs of moderate complexity can " | ||||
| | @ -1964,14 +1964,14 @@ msgid "" | |||
"making them difficult to read and understand." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1343 | ||||
#: ../Doc/howto/regex.rst:1345 | ||||
msgid "" | ||||
"For such REs, specifying the :const:`re.VERBOSE` flag when compiling the " | ||||
"regular expression can be helpful, because it allows you to format the " | ||||
"regular expression more clearly." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1347 | ||||
#: ../Doc/howto/regex.rst:1349 | ||||
msgid "" | ||||
"The ``re.VERBOSE`` flag has several effects. Whitespace in the regular " | ||||
"expression that *isn't* inside a character class is ignored. This means " | ||||
| | @ -1982,15 +1982,15 @@ msgid "" | |||
"quoted strings, this enables REs to be formatted more neatly::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/regex.rst:1364 | ||||
#: ../Doc/howto/regex.rst:1366 | ||||
msgid "This is far more readable than::" | ||||
msgstr "Ceci est beaucoup plus lisible que::" | ||||
| ||||
#: ../Doc/howto/regex.rst:1370 | ||||
#: ../Doc/howto/regex.rst:1372 | ||||
msgid "Feedback" | ||||
msgstr "Retour" | ||||
| ||||
#: ../Doc/howto/regex.rst:1372 | ||||
#: ../Doc/howto/regex.rst:1374 | ||||
msgid "" | ||||
"Regular expressions are a complicated topic. Did this document help you " | ||||
"understand them? Were there parts that were unclear, or Problems you " | ||||
| | @ -2002,7 +2002,7 @@ msgstr "" | |||
"problèmes que vous avez rencontrés ne sont pas traités ici ? Si tel est le " | ||||
"cas, merci d'envoyer vos suggestions d'améliorations à l'auteur." | ||||
| ||||
#: ../Doc/howto/regex.rst:1377 | ||||
#: ../Doc/howto/regex.rst:1379 | ||||
msgid "" | ||||
"The most complete book on regular expressions is almost certainly Jeffrey " | ||||
"Friedl's Mastering Regular Expressions, published by O'Reilly. " | ||||
| | | |||
| | @ -8,7 +8,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2018-04-29 00:24+0200\n" | ||||
"POT-Creation-Date: 2018-06-28 15:29+0200\n" | ||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" | ||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" | ||||
"Language-Team: LANGUAGE <LL@li.org>\n" | ||||
| | @ -342,16 +342,17 @@ msgstr "" | |||
#: ../Doc/howto/unicode.rst:218 | ||||
msgid "" | ||||
"To help understand the standard, Jukka Korpela has written `an introductory " | ||||
"guide <https://www.cs.tut.fi/~jkorpela/unicode/guide.html>`_ to reading the " | ||||
"Unicode character tables." | ||||
"guide <http://jkorpela.fi/unicode/guide.html>`_ to reading the Unicode " | ||||
"character tables." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/unicode.rst:222 | ||||
msgid "" | ||||
"Another `good introductory article <http://www.joelonsoftware.com/articles/" | ||||
"Unicode.html>`_ was written by Joel Spolsky. If this introduction didn't " | ||||
"make things clear to you, you should try reading this alternate article " | ||||
"before continuing." | ||||
"Another `good introductory article <https://www.joelonsoftware." | ||||
"com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-" | ||||
"positively-must-know-about-unicode-and-character-sets-no-excuses/>`_ was " | ||||
"written by Joel Spolsky. If this introduction didn't make things clear to " | ||||
"you, you should try reading this alternate article before continuing." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/unicode.rst:227 | ||||
| | @ -615,7 +616,7 @@ msgstr "" | |||
| ||||
#: ../Doc/howto/unicode.rst:492 | ||||
msgid "" | ||||
"`Pragmatic Unicode <http://nedbatchelder.com/text/unipain.html>`_, a PyCon " | ||||
"`Pragmatic Unicode <https://nedbatchelder.com/text/unipain.html>`_, a PyCon " | ||||
"2012 presentation by Ned Batchelder." | ||||
msgstr "" | ||||
| ||||
| | | |||
| | @ -8,7 +8,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2018-06-10 11:27+0200\n" | ||||
"POT-Creation-Date: 2018-06-28 15:29+0200\n" | ||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" | ||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" | ||||
"Language-Team: LANGUAGE <LL@li.org>\n" | ||||
| | @ -357,9 +357,9 @@ msgstr "" | |||
#: ../Doc/howto/urllib2.rst:413 | ||||
msgid "" | ||||
"Typical headers include 'Content-length', 'Content-type', and so on. See the " | ||||
"`Quick Reference to HTTP Headers <https://www.cs.tut.fi/~jkorpela/http." | ||||
"html>`_ for a useful listing of HTTP headers with brief explanations of " | ||||
"their meaning and use." | ||||
"`Quick Reference to HTTP Headers <http://jkorpela.fi/http.html>`_ for a " | ||||
"useful listing of HTTP headers with brief explanations of their meaning and " | ||||
"use." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/howto/urllib2.rst:420 | ||||
| | | |||
Loading…
Add table
Add a link
Reference in a new issue