--- rxvt-unicode/doc/rxvt.7.txt	2005/02/21 19:26:07	1.18
+++ rxvt-unicode/doc/rxvt.7.txt	2005/04/17 22:36:13	1.19
@@ -302,13 +302,16 @@
         representation of wchar_t. This is, of course, completely fine with
         respect to standards.
 
-        However, "__STDC_ISO_10646__" is the only sane way to support
-        multi-language apps in an OS, as using a locale-dependent (and
-        non-standardized) representation of wchar_t makes it impossible to
-        convert between wchar_t (as used by X11 and your applications) and
-        any other encoding without implementing OS-specific-wrappers for
-        each and every locale. There simply are no APIs to convert wchar_t
-        into anything except the current locale encoding.
+        However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1"
+        and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.
+
+        "__STDC_ISO_10646__" is the only sane way to support multi-language
+        apps in an OS, as using a locale-dependent (and non-standardized)
+        representation of wchar_t makes it impossible to convert between
+        wchar_t (as used by X11 and your applications) and any other
+        encoding without implementing OS-specific-wrappers for each and
+        every locale. There simply are no APIs to convert wchar_t into
+        anything except the current locale encoding.
 
         Some applications (such as the formidable mlterm) work around this
         by carrying their own replacement functions for character set
@@ -1669,13 +1672,14 @@
         fonts can be set manually or automatically.
 
     --with-codesets=NAME,...
-        Compile in support for additional codeset (encoding) groups (eu, vn
-        are always compiled in, which includes most 8-bit character sets).
-        These codeset tables are currently only used for driving X11 core
-        fonts, they are not required for Xft fonts. Compiling them in will
-        make your binary bigger (together about 700kB), but it doesn't
-        increase memory usage unless you use an X11 font requiring one of
-        these encodings.
+        Compile in support for additional codeset (encoding) groups ("eu",
+        "vn" are always compiled in, which includes most 8-bit character
+        sets). These codeset tables are used for driving X11 core fonts,
+        they are not required for Xft fonts, although having them compiled
+        in lets rxvt-unicode choose replacement fonts more intelligently.
+        Compiling them in will make your binary bigger (all of together cost
+        about 700kB), but it doesn't increase memory usage unless you use a
+        font requiring one of these encodings.
 
            all             all available codeset groups 
            zh              common chinese encodings 
@@ -1836,6 +1840,7 @@
           tripleclickwords
           settable insecure mode
           keysym remapping support
+          cursor blinking and underline cursor
           -embed and -pty-fd options
 
     --enable-iso14755
@@ -1876,9 +1881,6 @@
         hot keys. This should keep in a fixed position the rxvt corner which
         is closest to a corner of the screen.
 
-    --enable-cursor-blink
-        Add support for a blinking cursor.
-
     --enable-pointer-blank
         Add support to have the pointer disappear when typing or inactive.