--- rxvt-unicode/doc/rxvt.7.man.in	2005/04/17 22:36:13	1.20
+++ rxvt-unicode/doc/rxvt.7.man.in	2005/06/30 14:00:49	1.21
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
+.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -129,7 +129,7 @@
 .\" ========================================================================
 .\"
 .IX Title "rxvt 7"
-.TH rxvt 7 "2005-04-17" "5.3" "RXVT-UNICODE"
+.TH rxvt 7 "2005-06-26" "5.6" "RXVT-UNICODE"
 .SH "NAME"
 RXVT REFERENCE \- FAQ, command sequences and other background information
 .SH "SYNOPSIS"
@@ -408,6 +408,15 @@
 .Sp
 All of this is not a problem when using X11 core fonts, as their bounding
 box data is correct.
+.IP "On Solaris 9, many line-drawing characters are too wide." 4
+.IX Item "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:
+.Sp
+.Vb 1
+\&   #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
+.Ve
 .IP "My Compose (Multi_key) key is no longer working." 4
 .IX Item "My Compose (Multi_key) key is no longer working."
 The most common causes for this are that either your locale is not set
@@ -479,6 +488,10 @@
 The rxvt-unicode author insists that the right way to fix this is in the
 system libraries once and for all, instead of forcing every app to carry
 complete replacements for them :)
+.IP "I use Solaris 9 and it doesn't compile/work/etc." 4
+.IX Item "I use Solaris 9 and it doesn't compile/work/etc."
+Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst
+problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem.
 .IP "How does rxvt-unicode determine the encoding to use?" 4
 .IX Item "How does rxvt-unicode determine the encoding to use?"
 .PD 0