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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.109 by root, Tue Jan 31 21:06:26 2006 UTC vs.
Revision 1.110 by root, Tue Jan 31 21:10:44 2006 UTC

… …
236 -set _NET_WM_WINDOW_OPACITY 0xc0000000 236 -set _NET_WM_WINDOW_OPACITY 0xc0000000
237 237
238Then click on a window you want to make transparent. Replace C<0xc0000000> 238Then click on a window you want to make transparent. Replace C<0xc0000000>
239by other values to change the degree of opacity. If it doesn't work and 239by other values to change the degree of opacity. If it doesn't work and
240your server crashes, you got to keep the pieces. 240your server crashes, you got to keep the pieces.
241
242=head3 Why do some chinese characters look so different than others?
243
244This is because there is a difference between script and language --
245rxvt-unicode does not know which language the text that is output is,
246as it only knows the unicode character codes. If rxvt-unicode first
247sees a japanese/chinese character, it might choose a japanese font for
248display. Subsequent japanese characters will use that font. Now, many
249chinese characters aren't represented in japanese fonts, so when the first
250non-japanese character comes up, rxvt-unicode will look for a chinese font
251-- unfortunately at this point, it will still use the japanese font for
252chinese characters that are also in the japanese font.
253
254The workaround is easy: just tag a chinese font at the end of your font
255list (see the previous question). The key is to view the font list as
256a preference list: If you expect more japanese, list a japanese font
257first. If you expect more chinese, put a chinese font first.
258
259In the future it might be possible to switch language preferences at
260runtime (the internal data structure has no problem with using different
261fonts for the same character at the same time, but no interface for this
262has been designed yet).
263
264Until then, you might get away with switching fonts at runtime (see L<Can
265I switch the fonts at runtime?> later in this document).
266 241
267=head3 Why does rxvt-unicode sometimes leave pixel droppings? 242=head3 Why does rxvt-unicode sometimes leave pixel droppings?
268 243
269Most fonts were not designed for terminal use, which means that character 244Most fonts were not designed for terminal use, which means that character
270size varies a lot. A font that is otherwise fine for terminal use might 245size varies a lot. A font that is otherwise fine for terminal use might
… …
412 URxvt.color15: #e1dddd 387 URxvt.color15: #e1dddd
413 388
414They have been described (not by me) as "pretty girly". 389They have been described (not by me) as "pretty girly".
415 390
416=head3 Why do some characters look so much different than others? 391=head3 Why do some characters look so much different than others?
417 392
418See next entry. 393See next entry.
419 394
420=head3 How does rxvt-unicode choose fonts? 395=head3 How does rxvt-unicode choose fonts?
421 396
422Most fonts do not contain the full range of Unicode, which is 397Most fonts do not contain the full range of Unicode, which is
423fine. Chances are that the font you (or the admin/package maintainer of 398fine. Chances are that the font you (or the admin/package maintainer of
424your system/os) have specified does not cover all the characters you want 399your system/os) have specified does not cover all the characters you want
425to display. 400to display.
426 401
427B<rxvt-unicode> makes a best-effort try at finding a replacement 402B<rxvt-unicode> makes a best-effort try at finding a replacement
428font. Often the result is fine, but sometimes the chosen font looks 403font. Often the result is fine, but sometimes the chosen font looks
429bad/ugly/wrong. Some fonts have totally strange characters that don't 404bad/ugly/wrong. Some fonts have totally strange characters that don't
430resemble the correct glyph at all, and rxvt-unicode lacks the artificial 405resemble the correct glyph at all, and rxvt-unicode lacks the artificial
431intelligence to detect that a specific glyph is wrong: it has to believe 406intelligence to detect that a specific glyph is wrong: it has to believe
432the font that the characters it claims to contain indeed look correct. 407the font that the characters it claims to contain indeed look correct.
433 408
434In that case, select a font of your taste and add it to the font list, 409In that case, select a font of your taste and add it to the font list,
435e.g.: 410e.g.:
436 411
437 @@URXVT_NAME@@ -fn basefont,font2,font3... 412 @@URXVT_NAME@@ -fn basefont,font2,font3...
438 413
439When rxvt-unicode sees a character, it will first look at the base 414When rxvt-unicode sees a character, it will first look at the base
440font. If the base font does not contain the character, it will go to the 415font. If the base font does not contain the character, it will go to the
441next font, and so on. Specifying your own fonts will also speed up this 416next font, and so on. Specifying your own fonts will also speed up this
442search and use less resources within rxvt-unicode and the X-server. 417search and use less resources within rxvt-unicode and the X-server.
443 418
444The only limitation is that none of the fonts may be larger than the base 419The only limitation is that none of the fonts may be larger than the base
445font, as the base font defines the terminal character cell size, which 420font, as the base font defines the terminal character cell size, which
446must be the same due to the way terminals work. 421must be the same due to the way terminals work.
422
423=head3 Why do some chinese characters look so different than others?
424
425This is because there is a difference between script and language --
426rxvt-unicode does not know which language the text that is output is,
427as it only knows the unicode character codes. If rxvt-unicode first
428sees a japanese/chinese character, it might choose a japanese font for
429display. Subsequent japanese characters will use that font. Now, many
430chinese characters aren't represented in japanese fonts, so when the first
431non-japanese character comes up, rxvt-unicode will look for a chinese font
432-- unfortunately at this point, it will still use the japanese font for
433chinese characters that are also in the japanese font.
434
435The workaround is easy: just tag a chinese font at the end of your font
436list (see the previous question). The key is to view the font list as
437a preference list: If you expect more japanese, list a japanese font
438first. If you expect more chinese, put a chinese font first.
439
440In the future it might be possible to switch language preferences at
441runtime (the internal data structure has no problem with using different
442fonts for the same character at the same time, but no interface for this
443has been designed yet).
444
445Until then, you might get away with switching fonts at runtime (see L<Can
446I switch the fonts at runtime?> later in this document).
447 447
448=head2 Keyboard, Mouse & User Interaction 448=head2 Keyboard, Mouse & User Interaction
449 449
450=head3 The new selection selects pieces that are too big, how can I select single words? 450=head3 The new selection selects pieces that are too big, how can I select single words?
451 451
… …
1005encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited 1005encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
1006to 8-bit encodings. 1006to 8-bit encodings.
1007 1007
1008=head1 RXVT-UNICODE TECHNICAL REFERENCE 1008=head1 RXVT-UNICODE TECHNICAL REFERENCE
1009 1009
1010=head1 DESCRIPTION
1011
1012The rest of this document describes various technical aspects of 1010The rest of this document describes various technical aspects of
1013B<rxvt-unicode>. First the description of supported command sequences, 1011B<rxvt-unicode>. First the description of supported command sequences,
1014followed by pixmap support and last by a description of all features 1012followed by pixmap support and last by a description of all features
1015selectable at C<configure> time. 1013selectable at C<configure> time.
1016 1014
1017=head1 Definitions 1015=head2 Definitions
1018 1016
1019=over 4 1017=over 4
1020 1018
1021=item B<< C<c> >> 1019=item B<< C<c> >>
1022 1020
… …
1040 1038
1041A text parameter composed of printable characters. 1039A text parameter composed of printable characters.
1042 1040
1043=back 1041=back
1044 1042
1045=head1 Values 1043=head2 Values
1046 1044
1047=over 4 1045=over 4
1048 1046
1049=item B<< C<ENQ> >> 1047=item B<< C<ENQ> >>
1050 1048
… …
1093 1091
1094Space Character 1092Space Character
1095 1093
1096=back 1094=back
1097 1095
1098=head1 Escape Sequences 1096=head2 Escape Sequences
1099 1097
1100=over 4 1098=over 4
1101 1099
1102=item B<< C<ESC # 8> >> 1100=item B<< C<ESC # 8> >>
1103 1101
… …
1201 1199
1202=back 1200=back
1203 1201
1204X<CSI> 1202X<CSI>
1205 1203
1206=head1 CSI (Command Sequence Introducer) Sequences 1204=head2 CSI (Command Sequence Introducer) Sequences
1207 1205
1208=over 4 1206=over 4
1209 1207
1210=item B<< C<ESC [ Ps @> >> 1208=item B<< C<ESC [ Ps @> >>
1211 1209
… …
1481 1479
1482=back 1480=back
1483 1481
1484X<PrivateModes> 1482X<PrivateModes>
1485 1483
1486=head1 DEC Private Modes 1484=head2 DEC Private Modes
1487 1485
1488=over 4 1486=over 4
1489 1487
1490=item B<< C<ESC [ ? Pm h> >> 1488=item B<< C<ESC [ ? Pm h> >>
1491 1489
… …
1755 1753
1756=back 1754=back
1757 1755
1758X<XTerm> 1756X<XTerm>
1759 1757
1760=head1 XTerm Operating System Commands 1758=head2 XTerm Operating System Commands
1761 1759
1762=over 4 1760=over 4
1763 1761
1764=item B<< C<ESC ] Ps;Pt ST> >> 1762=item B<< C<ESC ] Ps;Pt ST> >>
1765 1763
… …
1802 B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl). 1800 B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl).
1803 1801
1804=end table 1802=end table
1805 1803
1806=back 1804=back
1807
1808X<XPM>
1809 1805
1810=head1 XPM 1806=head1 XPM
1811 1807
1812For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value 1808For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
1813of B<< C<Pt> >> can be the name of the background pixmap followed by a 1809of B<< C<Pt> >> can be the name of the background pixmap followed by a

Diff Legend

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