ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.txt
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.7.txt (file contents):
Revision 1.73 by root, Thu Jul 6 18:56:10 2006 UTC vs.
Revision 1.74 by root, Thu Jul 6 19:43:21 2006 UTC

… …
292 You can think of this as a kind of manual ISO-2022 switching. 292 You can think of this as a kind of manual ISO-2022 switching.
293 293
294 Why do italic characters look as if clipped? 294 Why do italic characters look as if clipped?
295 Many fonts have difficulties with italic characters and hinting. For 295 Many fonts have difficulties with italic characters and hinting. For
296 example, the otherwise very nicely hinted font "xft:Bitstream Vera Sans 296 example, the otherwise very nicely hinted font "xft:Bitstream Vera Sans
297 Mono" completely fails in it's italic face. A workaround might be to 297 Mono" completely fails in its italic face. A workaround might be to
298 enable freetype autohinting, i.e. like this: 298 enable freetype autohinting, i.e. like this:
299 299
300 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 300 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
301 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 301 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
302 302
… …
306 antialiasing (by appending ":antialias=false"), which saves lots of 306 antialiasing (by appending ":antialias=false"), which saves lots of
307 memory and also speeds up rendering considerably. 307 memory and also speeds up rendering considerably.
308 308
309 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? 309 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
310 Rxvt-unicode will use whatever you specify as a font. If it needs to 310 Rxvt-unicode will use whatever you specify as a font. If it needs to
311 fall back to it's default font search list it will prefer X11 core 311 fall back to its default font search list it will prefer X11 core fonts,
312 fonts, because they are small and fast, and then use Xft fonts. It has 312 because they are small and fast, and then use Xft fonts. It has
313 antialiasing disabled for most of them, because the author thinks they 313 antialiasing disabled for most of them, because the author thinks they
314 look best that way. 314 look best that way.
315 315
316 If you want antialiasing, you have to specify the fonts manually. 316 If you want antialiasing, you have to specify the fonts manually.
317 317
… …
859 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ 859 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
860 :vs=\E[?25h: 860 :vs=\E[?25h:
861 861
862 Why does "ls" no longer have coloured output? 862 Why does "ls" no longer have coloured output?
863 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 863 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to
864 decide wether a terminal has colour, but uses it's own configuration 864 decide wether a terminal has colour, but uses its own configuration
865 file. Needless to say, "rxvt-unicode" is not in it's default file (among 865 file. Needless to say, "rxvt-unicode" is not in its default file (among
866 with most other terminals supporting colour). Either add: 866 with most other terminals supporting colour). Either add:
867 867
868 TERM rxvt-unicode 868 TERM rxvt-unicode
869 869
870 to "/etc/DIR_COLORS" or simply add: 870 to "/etc/DIR_COLORS" or simply add:
… …
935 The reasons is that there exists a perfectly fine mechanism for 935 The reasons is that there exists a perfectly fine mechanism for
936 selecting the encoding, doing I/O and (most important) communicating 936 selecting the encoding, doing I/O and (most important) communicating
937 this to all applications so everybody agrees on character properties 937 this to all applications so everybody agrees on character properties
938 such as width and code number. This mechanism is the *locale*. 938 such as width and code number. This mechanism is the *locale*.
939 Applications not using that info will have problems (for example, 939 Applications not using that info will have problems (for example,
940 "xterm" gets the width of characters wrong as it uses it's own, 940 "xterm" gets the width of characters wrong as it uses its own,
941 locale-independent table under all locales). 941 locale-independent table under all locales).
942 942
943 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. All 943 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. All
944 programs doing the same (that is, most) will automatically agree in the 944 programs doing the same (that is, most) will automatically agree in the
945 interpretation of characters. 945 interpretation of characters.
… …
1090 your compile environment, or an implementation that implements it, 1090 your compile environment, or an implementation that implements it,
1091 wether it defines the symbol or not. "__STDC_ISO_10646__" requires that 1091 wether it defines the symbol or not. "__STDC_ISO_10646__" requires that
1092 wchar_t is represented as unicode. 1092 wchar_t is represented as unicode.
1093 1093
1094 As you might have guessed, FreeBSD does neither define this symobl nor 1094 As you might have guessed, FreeBSD does neither define this symobl nor
1095 does it support it. Instead, it uses it's own internal representation of 1095 does it support it. Instead, it uses its own internal representation of
1096 wchar_t. This is, of course, completely fine with respect to standards. 1096 wchar_t. This is, of course, completely fine with respect to standards.
1097 1097
1098 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and 1098 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and
1099 "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. 1099 "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.
1100 1100

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines