--- rxvt-unicode/doc/rxvt.7.pod 2005/02/17 12:00:33 1.48 +++ rxvt-unicode/doc/rxvt.7.pod 2005/07/13 01:24:09 1.57 @@ -260,6 +260,14 @@ All of this is not a problem when using X11 core fonts, as their bounding box data is correct. +=item On Solaris 9, many line-drawing characters are too wide. + +Seems to be a known bug, read +L. Some people use the +following ugly workaround to get non-double-wide-characters working: + + #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) + =item My Compose (Multi_key) key is no longer working. The most common causes for this are that either your locale is not set @@ -312,13 +320,16 @@ does it support it. Instead, it uses it's own internal representation of B. This is, of course, completely fine with respect to standards. -However, C<__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 B makes it impossible to -convert between B (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 B into anything -except the current locale encoding. +However, that means rxvt-unicode only works in C, C and +C locales under FreeBSD (which all use Unicode as B. + +C<__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 B makes it impossible to convert between +B (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 B into anything except the current +locale encoding. Some applications (such as the formidable B) work around this by carrying their own replacement functions for character set handling @@ -330,6 +341,24 @@ system libraries once and for all, instead of forcing every app to carry complete replacements for them :) +=item I use Solaris 9 and it doesn't compile/work/etc. + +Try the diff in F as a base. It fixes the worst +problems with C and a compile problem. + +=item How can I use rxvt-unicode under cygwin? + +rxvt-unicode should compile and run out of the box on cygwin, using +the X11 libraries that come with cygwin. libW11 emulation is no +longer supported (and makes no sense, either, as it only supported a +single font). I recommend starting the X-server in C<-multiwindow> or +C<-rootless> mode instead, which will result in similar look&feel as the +old libW11 emulation. + +At the time of this writing, cygwin didn't seem to support any multi-byte +encodings (you might try C), so you are likely limited +to 8-bit encodings. + =item How does rxvt-unicode determine the encoding to use? =item Is there an option to switch encodings? @@ -1477,19 +1506,21 @@ B<< C >> Change colour of bold characters to B<< C >> B<< C >> Change colour of underlined characters to B<< C >> B<< C >> Change default background to B<< C >> - B<< C >> Change default foreground colour to B<< C >> I + B<< C >> Change default foreground colour to B<< C >>. B<< C >> Change Log File to B<< C >> I - B<< C >> Change default background colour to B<< C >> I + B<< C >> Change default background colour to B<< C >>. B<< C >> Set fontset to B<< C >>, with the following special values of B<< C >> (B) B<< C<#+n> >> change up B<< C >> B<< C<#-n> >> change down B<< C >> if B<< C >> is missing of 0, a value of 1 is used I change to font0 B<< C >> change to font B<< C >> B<< C >> Log all scrollback buffer and all of screen to B<< C >> - B<< C >> Change current locale to B<< C >>, or, if B<< C >> is B<< C >>, return the current locale (@@RXVT_NAME@@ extension) - B<< C >> Menubar command B<< C >> I (rxvt-unicode extension) + B<< C >> Change current locale to B<< C >>, or, if B<< C >> is B<< C >>, return the current locale (Compile frills). + B<< C >> Menubar command B<< C >> (Compile menubar). B<< C >> Change colour of italic characters to B<< C >> - B<< C >> Change background pixmap tint colour to B<< C >> + B<< C >> Change background pixmap tint colour to B<< C >> (Compile transparency). B<< C >> Set normal fontset to B<< C >>. Same as C. - B<< C >> Set bold fontset to B<< C >>. Similar to C. - B<< C >> Set italic fontset to B<< C >>. Similar to C. - B<< C >> Set bold-italic fontset to B<< C >>. Similar to C. + B<< C >> Set bold fontset to B<< C >>. Similar to C (Compile styles). + B<< C >> Set italic fontset to B<< C >>. Similar to C (Compile styles). + B<< C >> Set bold-italic fontset to B<< C >>. Similar to C (Compile styles). + B<< C >> Move viewing window up by B<< C >> lines, or clear scrollback buffer if C (Compile frills). + B<< C >> Move viewing window down by B<< C >> lines, or clear scrollback buffer if C (Compile frills). =end table @@ -2184,12 +2215,13 @@ =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 (C, C +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. =begin table @@ -2370,16 +2402,18 @@ in combination with other switches) is: MWM-hints + EWMH-hints (pid, utf8 names) and protocols (ping) seperate underline colour settable border widths and borderless switch settable extra linespacing - extra window properties (e.g. UTF-8 window names and PID) iso-14755-2 and -3, and visual feedback backindex and forwardindex escape sequence - window op and locale change escape sequences + window op and some xterm/OSC escape sequences tripleclickwords settable insecure mode keysym remapping support + cursor blinking and underline cursor + -embed and -pty-fd options =item --enable-iso14755 @@ -2428,10 +2462,6 @@ keys. This should keep in a fixed position the rxvt corner which is closest to a corner of the screen. -=item --enable-cursor-blink - -Add support for a blinking cursor. - =item --enable-pointer-blank Add support to have the pointer disappear when typing or inactive.