--- rxvt-unicode/README.unicode 2003/11/24 17:28:07 1.1 +++ rxvt-unicode/README.unicode 2004/02/25 12:38:30 1.6 @@ -1,16 +1,32 @@ Sketchy overview of the details: -- gcc is probably required to compile this release, g++, too, as it has - been re-written in C++. +- gcc-3.x is probably required to compile this release, g++-3.x, too, as it + has been re-written in C++ (and a corresponding version of libstdc++). - the options used in the ./reconf script should work. everything else - might be broken. + might work and might be broken. -- wchar_t MUST be UNICODE or ISO-10646-1 on your system, or various - things will break down. - -- rxvt ALWAYS expects utf-8 input, regardless of the locale, currently. - so only start it in a utf-8-locale: "LC_CTYPE=en_US.UTF-8 rxvt" etc.. +- wchar_t MUST be UNICODE or ISO-10646-1 on your system, or various things + will break down. On GNU/Linux, this is true for all locales, on Solaris, + this might be true only for locales ending in "@ucs", but you should + have plenty of them, as there should be a corresponding @ucs-locale for + every normal locale. + + If you know details for other operating systems, please notify me (in + general, if your env defines __STDC_ISO_10646__ then everything should + be fine). + +- rxvt will use unicode internally, but does input/output in the current + locale. so to get a utf-8 terminal, use "LC_CTYPE=en_US.UTF-8 rxvt" or + equivalent. + +- you can specify a different locale to be used for your input method + using the imLocale ressource or switch, e.g.: + LC_CTYPE=ja_JP.UTF-8 rxvt -imlocale ja_JP.EUC-JP + +- keyboard input is limited by the selected locale (and X's support for it), + tty input and output likewise. selection support is mostly independent + of the locale. - "-fn" commandline switch and *.font ressource accepts a comma seperated list of fontnames: @@ -20,9 +36,10 @@ xft:Andale Mono a xft font xft:Andale Mono:pixelsize=20 -- the _first_ font in the list selects the cell width/height. All other fonts - must be smaller or same sized, or they will be ignored or worse. xft fonts - will automatically be rescaled. +- the _first_ font in the list selects the cell width/height. All other + fonts must be smaller or same sized, or they will be ignored or worse. + xft fonts will automatically be rescaled, x11-fonts, too, if their + size is not specified in the XLFD. - the fonts will be tried in the order given when searching for a font to display a specific character. if you are e.g. mainly interested in @@ -31,10 +48,19 @@ only want to display other characters you should put a ascii/is8859 text font first (e.g. "9x15bold") and let rxvt sort it out. -- xft fonts require gobs of memory and generally are slow +- xft fonts require gobs of memory and generally are slow. try not to + antialias them ("Font:antialias=false") when possible. Often looks + better, too, as they then match other fonts in weight. + +- src/defaultfont.C lists the fallback fonts that are tried when a + character cannot be displayed with the current list of fonts. + +- using bold fonts for the bold attribute is not supported by xft + and will not be supported by rxvt-unicode, either, even for normal x11 + fonts. -- src/defaultfont.C lists the fallback fonts that are tried when a character cannot - be displayed with the current list of fonts. +- normal bold text will use reverse video unless the colorBD resource has + been set. coloured text will use high-intensity colours for bold. Marc