summaryrefslogtreecommitdiff
path: root/docs/src
diff options
context:
space:
mode:
authorgbrandl <devnull@localhost>2007-05-18 15:18:26 +0200
committergbrandl <devnull@localhost>2007-05-18 15:18:26 +0200
commitd99c181e758829d3e7beded434c7a58c0b7398d0 (patch)
tree382d3b1556d92ecfbe726b427b400db28e1d9203 /docs/src
parentfd856078ccab574327f688f9b63fff8428fa2752 (diff)
downloadpygments-d99c181e758829d3e7beded434c7a58c0b7398d0.tar.gz
[svn] Make a sentence clearer.
Diffstat (limited to 'docs/src')
-rw-r--r--docs/src/unicode.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/src/unicode.txt b/docs/src/unicode.txt
index 53ff8494..8184e2b2 100644
--- a/docs/src/unicode.txt
+++ b/docs/src/unicode.txt
@@ -11,7 +11,7 @@ If you pass a lexer a string object (not unicode), it tries to decode the data
using this encoding.
You can override the encoding using the `encoding` lexer option. If you have the
`chardet`_ library installed and set the encoding to ``chardet`` if will ananlyse
-the text and fetch the best encoding automatically:
+the text and use the encoding it thinks is the right one automatically:
.. sourcecode:: python
@@ -34,7 +34,8 @@ source and the output stream does not accept Unicode written to it!**
This is the case for all regular files and for terminals.
Note: The Terminal formatter tries to be smart: if its output stream has an
-`encoding` attribute, it will encode any Unicode string with this encoding
+`encoding` attribute, and you haven't set the option,
+it will encode any Unicode string with this encoding
before writing it. This is the case for `sys.stdout`, for example. The other
formatters don't have that behavior.