--- rxvt-unicode/README.FAQ	2005/02/17 12:06:21	1.12
+++ rxvt-unicode/README.FAQ	2005/06/30 14:00:49	1.14
@@ -228,6 +228,13 @@
         All of this is not a problem when using X11 core fonts, as their
         bounding box data is correct.
 
+    On Solaris 9, many line-drawing characters are too wide.
+        Seems to be a known bug, read
+        <http://nixdoc.net/files/forum/about34198.html>. Some people use the
+        following ugly workaround to get non-double-wide-characters working:
+
+           #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
+
     My Compose (Multi_key) key is no longer working.
         The most common causes for this are that either your locale is not
         set correctly, or you specified a preeditStyle that is not supported
@@ -281,13 +288,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
@@ -300,6 +310,10 @@
         the system libraries once and for all, instead of forcing every app
         to carry complete replacements for them :)
 
+    I use Solaris 9 and it doesn't compile/work/etc.
+        Try the diff in doc/solaris9.patch as a base. It fixes the worst
+        problems with "wcwidth" and a compile problem.
+
     How does rxvt-unicode determine the encoding to use?
     Is there an option to switch encodings?
         Unlike some other terminals, rxvt-unicode has no encoding switch,