11# SOME DESCRIPTIVE TITLE.
2- # Copyright (C) 2001-2018 , Python Software Foundation
2+ # Copyright (C) 2001-2019 , Python Software Foundation
33# This file is distributed under the same license as the Python package.
44# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
55#
@@ -18,7 +18,7 @@ msgid ""
1818msgstr ""
1919"Project-Id-Version : Python 3.7\n "
2020"Report-Msgid-Bugs-To : \n "
21- "POT-Creation-Date : 2018-11-01 09:38 +0900\n "
21+ "POT-Creation-Date : 2019-01-24 10:27 +0900\n "
2222"PO-Revision-Date : 2017-02-16 17:45+0000\n "
2323"
Last-Translator :
Danny Vi <[email protected] >, 2018\n "
2424"Language-Team : Chinese (China) (https://www.transifex.com/python-doc/teams/5390/zh_CN/)\n "
@@ -865,17 +865,17 @@ msgid ""
865865"The :func:`fileConfig` function takes a default parameter, "
866866"``disable_existing_loggers``, which defaults to ``True`` for reasons of "
867867"backward compatibility. This may or may not be what you want, since it will "
868- "cause any loggers existing before the :func:`fileConfig` call to be disabled "
869- " unless they (or an ancestor) are explicitly named in the configuration. "
870- "Please refer to the reference documentation for more information, and "
871- "specify ``False`` for this parameter if you wish."
868+ "cause any non-root loggers existing before the :func:`fileConfig` call to be"
869+ " disabled unless they (or an ancestor) are explicitly named in the "
870+ "configuration. Please refer to the reference documentation for more "
871+ "information, and specify ``False`` for this parameter if you wish."
872872msgstr ""
873873
874874#: ../../howto/logging.rst:703
875875msgid ""
876876"The dictionary passed to :func:`dictConfig` can also specify a Boolean value"
877877" with key ``disable_existing_loggers``, which if not specified explicitly in"
878- " the dictionary also defaults to being interpreted as ``True``. This leads "
878+ " the dictionary also defaults to being interpreted as ``True``. This leads "
879879"to the logger-disabling behaviour described above, which may not be what you"
880880" want - in which case, provide the key explicitly with a value of ``False``."
881881msgstr ""
@@ -988,7 +988,7 @@ msgid ""
988988"If for some reason you *don't* want these messages printed in the absence of"
989989" any logging configuration, you can attach a do-nothing handler to the top-"
990990"level logger for your library. This avoids the message being printed, since "
991- "a handler will be always be found for the library's events: it just doesn't "
991+ "a handler will always be found for the library's events: it just doesn't "
992992"produce any output. If the library user configures logging for application "
993993"use, presumably that configuration will add some handlers, and if levels are"
994994" suitably configured then logging calls made in library code will send "
0 commit comments