diff options
author | Vinay Sajip <vinay_sajip@yahoo.co.uk> | 2012-07-27 09:54:10 (GMT) |
---|---|---|
committer | Vinay Sajip <vinay_sajip@yahoo.co.uk> | 2012-07-27 09:54:10 (GMT) |
commit | a58d668fd92bab2265979784ef8edb9c3ea3f093 (patch) | |
tree | 725c3096bdeb37ea3365a21c6212fd5ce07b2c5d /Doc/howto | |
parent | e708a8a4aa3bda35a6720d0635a7468fb7a63b81 (diff) | |
download | cpython-a58d668fd92bab2265979784ef8edb9c3ea3f093.zip cpython-a58d668fd92bab2265979784ef8edb9c3ea3f093.tar.gz cpython-a58d668fd92bab2265979784ef8edb9c3ea3f093.tar.bz2 |
Improved cookbook entry and fixed typo.
Diffstat (limited to 'Doc/howto')
-rw-r--r-- | Doc/howto/logging-cookbook.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Doc/howto/logging-cookbook.rst b/Doc/howto/logging-cookbook.rst index 59864a9..370c757 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 |