[Boost-commit] svn:boost r85083 - trunk/libs/log/doc

Subject: [Boost-commit] svn:boost r85083 - trunk/libs/log/doc
From: andrey.semashev_at_[hidden]
Date: 2013-07-19 17:26:00

Author: andysem
Date: 2013-07-19 17:26:00 EDT (Fri, 19 Jul 2013)
New Revision: 85083
URL: http://svn.boost.org/trac/boost/changeset/85083

Log:
Fixed typo.

Text files modified: 
   trunk/libs/log/doc/tutorial.qbk |     2 +-                                      
   1 files changed, 1 insertions(+), 1 deletions(-)

Modified: trunk/libs/log/doc/tutorial.qbk
==============================================================================
--- trunk/libs/log/doc/tutorial.qbk	Fri Jul 19 10:41:41 2013	(r85082)
+++ trunk/libs/log/doc/tutorial.qbk	2013-07-19 17:26:00 EDT (Fri, 19 Jul 2013)	(r85083)
@@ -350,7 +350,7 @@
 
 The library supports logging strings containing national characters. There are basically two ways of doing this. On UNIX-like systems typically some multibyte character encoding (e.g. UTF-8) is used to represent national characters. In this case the library can be used just the way it is used for plain ASCII logging, no additional setup is required.
 
-On Windows the common practice is to use wide strings to represent national characters. Also, most of the system API is wide character oriented, which requires Windows-specific sinks to also support wide strings. On the other hand, generic sinks, like [link log.detailed.sink_backends.text_file text file sink, are byte-oriented (because, well, you store bytes in files, not characters). This forces the library to perform character code conversion when needed by the sink. To set up the library for this one has to imbue the sink with a locale with the appropriate `codecvt` facet. __boost_locale__ can be used to generate such a locale. Let's see an example:
+On Windows the common practice is to use wide strings to represent national characters. Also, most of the system API is wide character oriented, which requires Windows-specific sinks to also support wide strings. On the other hand, generic sinks, like the [link log.detailed.sink_backends.text_file text file sink], are byte-oriented (because, well, you store bytes in files, not characters). This forces the library to perform character code conversion when needed by the sink. To set up the library for this one has to imbue the sink with a locale with the appropriate `codecvt` facet. __boost_locale__ can be used to generate such a locale. Let's see an example:
 
 [example_wide_char_logging_initialization]