From: Vinay Sajip Date: Fri, 27 Jul 2012 09:54:10 +0000 (+0100) Subject: Improved cookbook entry and fixed typo. X-Git-Tag: v3.3.0b2~101^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a58d668fd92bab2265979784ef8edb9c3ea3f093;p=thirdparty%2FPython%2Fcpython.git Improved cookbook entry and fixed typo. --- diff --git a/Doc/howto/logging-cookbook.rst b/Doc/howto/logging-cookbook.rst index 59864a9adcb6..370c7573bb95 100644 --- a/Doc/howto/logging-cookbook.rst +++ b/Doc/howto/logging-cookbook.rst @@ -1562,7 +1562,7 @@ appear before it. As this behaviour is broken, the incorrect BOM insertion code is being removed from Python 3.2.4 and later. However, it is not being replaced, and if you -want to produce RFC 5424-compliant messages which includes a BOM, an optional +want to produce RFC 5424-compliant messages which include a BOM, an optional pure-ASCII sequence before it and arbitrary Unicode after it, encoded using UTF-8, then you need to do the following: @@ -1580,8 +1580,8 @@ UTF-8, then you need to do the following: way, it will remain unchanged after UTF-8 encoding). #. Replace the Unicode section with whatever placeholders you like; if the data - which appears there after substitution is Unicode, that's fine -- it will be - encoded using UTF-8. + which appears there after substitution contains characters outside the ASCII + range, that's fine -- it will be encoded using UTF-8. The formatted message *will* be encoded using UTF-8 encoding by ``SysLogHandler``. If you follow the above rules, you should be able to produce