--- rxvt-unicode/doc/rxvt.7.man.in 2005/02/21 19:26:06 1.19 +++ 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-02-21" "5.2" "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 +. 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 @@ -459,13 +468,16 @@ does it support it. Instead, it uses it's own internal representation of \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. .Sp -However, \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support -multi-language apps in an \s-1OS\s0, as using a locale-dependent (and -non\-standardized) representation of \fBwchar_t\fR makes it impossible to -convert between \fBwchar_t\fR (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 \fBwchar_t\fR into anything -except the current locale encoding. +However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and +\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. +.Sp +\&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language +apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized) +representation of \fBwchar_t\fR makes it impossible to convert between +\&\fBwchar_t\fR (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 \fBwchar_t\fR into anything except the current +locale encoding. .Sp Some applications (such as the formidable \fBmlterm\fR) work around this by carrying their own replacement functions for character set handling @@ -476,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 @@ -2189,12 +2205,13 @@ styles. The fonts can be set manually or automatically. .IP "\-\-with\-codesets=NAME,..." 4 .IX Item "--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 (\f(CW\*(C`eu\*(C'\fR, \f(CW\*(C`vn\*(C'\fR +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. .TS l l . all all available codeset groups @@ -2346,7 +2363,7 @@ A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly in combination with other switches) is: .Sp -.Vb 12 +.Vb 13 \& MWM-hints \& EWMH-hints (pid, utf8 names) and protocols (ping) \& seperate underline colour @@ -2358,6 +2375,7 @@ \& tripleclickwords \& settable insecure mode \& keysym remapping support +\& cursor blinking and underline cursor \& -embed and -pty-fd options .Ve .IP "\-\-enable\-iso14755" 4 @@ -2399,9 +2417,6 @@ Add smart growth/shrink behaviour when changing font size via from hot keys. This should keep in a fixed position the rxvt corner which is closest to a corner of the screen. -.IP "\-\-enable\-cursor\-blink" 4 -.IX Item "--enable-cursor-blink" -Add support for a blinking cursor. .IP "\-\-enable\-pointer\-blank" 4 .IX Item "--enable-pointer-blank" Add support to have the pointer disappear when typing or inactive.