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

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

… …
126. ds Ae AE 126. ds Ae AE
127.\} 127.\}
128.rm #[ #] #H #V #F C 128.rm #[ #] #H #V #F C
129.\" ======================================================================== 129.\" ========================================================================
130.\" 130.\"
131.IX Title "rxvt 7" 131.IX Title "@@RXVT_NAME@@ 7"
132.TH rxvt 7 "2006-07-06" "7.7" "RXVT-UNICODE" 132.TH @@RXVT_NAME@@ 7 "2006-07-06" "7.7" "RXVT-UNICODE"
133.SH "NAME" 133.SH "NAME"
134RXVT REFERENCE \- FAQ, command sequences and other background information 134RXVT REFERENCE \- FAQ, command sequences and other background information
135.SH "SYNOPSIS" 135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS" 136.IX Header "SYNOPSIS"
137.Vb 2 137.Vb 2
… …
484\fIWhy do italic characters look as if clipped?\fR 484\fIWhy do italic characters look as if clipped?\fR
485.IX Subsection "Why do italic characters look as if clipped?" 485.IX Subsection "Why do italic characters look as if clipped?"
486.PP 486.PP
487Many fonts have difficulties with italic characters and hinting. For 487Many fonts have difficulties with italic characters and hinting. For
488example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans 488example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans
489Mono\*(C'\fR completely fails in it's italic face. A workaround might be to 489Mono\*(C'\fR completely fails in its italic face. A workaround might be to
490enable freetype autohinting, i.e. like this: 490enable freetype autohinting, i.e. like this:
491.PP 491.PP
492.Vb 2 492.Vb 2
493\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 493\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
494\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 494\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
… …
504.PP 504.PP
505\fIRxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?\fR 505\fIRxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?\fR
506.IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 506.IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
507.PP 507.PP
508Rxvt-unicode will use whatever you specify as a font. If it needs to 508Rxvt-unicode will use whatever you specify as a font. If it needs to
509fall back to it's default font search list it will prefer X11 core 509fall back to its default font search list it will prefer X11 core
510fonts, because they are small and fast, and then use Xft fonts. It has 510fonts, because they are small and fast, and then use Xft fonts. It has
511antialiasing disabled for most of them, because the author thinks they 511antialiasing disabled for most of them, because the author thinks they
512look best that way. 512look best that way.
513.PP 513.PP
514If you want antialiasing, you have to specify the fonts manually. 514If you want antialiasing, you have to specify the fonts manually.
… …
1165.PP 1165.PP
1166\fIWhy does \f(CI\*(C`ls\*(C'\fI no longer have coloured output?\fR 1166\fIWhy does \f(CI\*(C`ls\*(C'\fI no longer have coloured output?\fR
1167.IX Subsection "Why does ls no longer have coloured output?" 1167.IX Subsection "Why does ls no longer have coloured output?"
1168.PP 1168.PP
1169The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to 1169The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to
1170decide wether a terminal has colour, but uses it's own configuration 1170decide wether a terminal has colour, but uses its own configuration
1171file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among 1171file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in its default file (among
1172with most other terminals supporting colour). Either add: 1172with most other terminals supporting colour). Either add:
1173.PP 1173.PP
1174.Vb 1 1174.Vb 1
1175\& TERM rxvt\-unicode 1175\& TERM rxvt\-unicode
1176.Ve 1176.Ve
… …
1261The reasons is that there exists a perfectly fine mechanism for selecting 1261The reasons is that there exists a perfectly fine mechanism for selecting
1262the encoding, doing I/O and (most important) communicating this to all 1262the encoding, doing I/O and (most important) communicating this to all
1263applications so everybody agrees on character properties such as width 1263applications so everybody agrees on character properties such as width
1264and code number. This mechanism is the \fIlocale\fR. Applications not using 1264and code number. This mechanism is the \fIlocale\fR. Applications not using
1265that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of 1265that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of
1266characters wrong as it uses it's own, locale-independent table under all 1266characters wrong as it uses its own, locale-independent table under all
1267locales). 1267locales).
1268.PP 1268.PP
1269Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All 1269Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All
1270programs doing the same (that is, most) will automatically agree in the 1270programs doing the same (that is, most) will automatically agree in the
1271interpretation of characters. 1271interpretation of characters.
… …
1445in your compile environment, or an implementation that implements it, 1445in your compile environment, or an implementation that implements it,
1446wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that 1446wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that
1447\&\fBwchar_t\fR is represented as unicode. 1447\&\fBwchar_t\fR is represented as unicode.
1448.PP 1448.PP
1449As you might have guessed, FreeBSD does neither define this symobl nor 1449As you might have guessed, FreeBSD does neither define this symobl nor
1450does it support it. Instead, it uses it's own internal representation of 1450does it support it. Instead, it uses its own internal representation of
1451\&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. 1451\&\fBwchar_t\fR. This is, of course, completely fine with respect to standards.
1452.PP 1452.PP
1453However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and 1453However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and
1454\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. 1454\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR.
1455.PP 1455.PP

Diff Legend

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