<li><a href="#rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></li>
<li><a href="#what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></li>
<li><a href="#i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors. How do I change them?</a></li>
- <li><a href="#how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></li>
+ <li><a href="#why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></li>
</ul>
<li><a href="#keyboard__mouse___user_interaction">Keyboard, Mouse & User Interaction</a></li>
URxvt.color14: #73f7ff
URxvt.color7: #e1dddd
URxvt.color15: #e1dddd</pre>
-<p>(They were described (not by me) as ``pretty girly'').</p>
+<p>They have been described (not by me) as ``pretty girly''.</p>
<p>
</p>
-<h3><a name="how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></h3>
+<h3><a name="why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></h3>
+<pre>
+
+See next entry.</pre>
+<pre>
+
+=head3 How does rxvt-unicode choose fonts?</pre>
<pre>
Most fonts do not contain the full range of Unicode, which is
</dt>
<dd>
Look for the XPM includes in DIR.
+
+
</dd>
<p></p>
<dt><strong><a name="item__2d_2dwith_2dxpm_2dlibrary_3ddir">--with-xpm-library=DIR</a></strong><br />
by other values to change the degree of opacity. If it doesn't work and
your server crashes, you got to keep the pieces.
.PP
-\fIWhy do some chinese characters look so different than others?\fR
-.IX Subsection "Why do some chinese characters look so different than others?"
-.PP
-This is because there is a difference between script and language \*(--
-rxvt-unicode does not know which language the text that is output is,
-as it only knows the unicode character codes. If rxvt-unicode first
-sees a japanese/chinese character, it might choose a japanese font for
-display. Subsequent japanese characters will use that font. Now, many
-chinese characters aren't represented in japanese fonts, so when the first
-non-japanese character comes up, rxvt-unicode will look for a chinese font
-\&\*(-- unfortunately at this point, it will still use the japanese font for
-chinese characters that are also in the japanese font.
-.PP
-The workaround is easy: just tag a chinese font at the end of your font
-list (see the previous question). The key is to view the font list as
-a preference list: If you expect more japanese, list a japanese font
-first. If you expect more chinese, put a chinese font first.
-.PP
-In the future it might be possible to switch language preferences at
-runtime (the internal data structure has no problem with using different
-fonts for the same character at the same time, but no interface for this
-has been designed yet).
-.PP
-Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document).
-.PP
\fIWhy does rxvt-unicode sometimes leave pixel droppings?\fR
.IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?"
.PP
The only limitation is that none of the fonts may be larger than the base
font, as the base font defines the terminal character cell size, which
must be the same due to the way terminals work.
+.PP
+\fIWhy do some chinese characters look so different than others?\fR
+.IX Subsection "Why do some chinese characters look so different than others?"
+.PP
+This is because there is a difference between script and language \*(--
+rxvt-unicode does not know which language the text that is output is,
+as it only knows the unicode character codes. If rxvt-unicode first
+sees a japanese/chinese character, it might choose a japanese font for
+display. Subsequent japanese characters will use that font. Now, many
+chinese characters aren't represented in japanese fonts, so when the first
+non-japanese character comes up, rxvt-unicode will look for a chinese font
+\&\*(-- unfortunately at this point, it will still use the japanese font for
+chinese characters that are also in the japanese font.
+.PP
+The workaround is easy: just tag a chinese font at the end of your font
+list (see the previous question). The key is to view the font list as
+a preference list: If you expect more japanese, list a japanese font
+first. If you expect more chinese, put a chinese font first.
+.PP
+In the future it might be possible to switch language preferences at
+runtime (the internal data structure has no problem with using different
+fonts for the same character at the same time, but no interface for this
+has been designed yet).
+.PP
+Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document).
.Sh "Keyboard, Mouse & User Interaction"
.IX Subsection "Keyboard, Mouse & User Interaction"
\fIThe new selection selects pieces that are too big, how can I select single words?\fR
to 8\-bit encodings.
.SH "RXVT-UNICODE TECHNICAL REFERENCE"
.IX Header "RXVT-UNICODE TECHNICAL REFERENCE"
-.SH "DESCRIPTION"
-.IX Header "DESCRIPTION"
The rest of this document describes various technical aspects of
\&\fBrxvt-unicode\fR. First the description of supported command sequences,
followed by pixmap support and last by a description of all features
selectable at \f(CW\*(C`configure\*(C'\fR time.
-.SH "Definitions"
-.IX Header "Definitions"
+.Sh "Definitions"
+.IX Subsection "Definitions"
.ie n .IP "\fB\fB""c""\fB\fR" 4
.el .IP "\fB\f(CBc\fB\fR" 4
.IX Item "c"
.el .IP "\fB\f(CBPt\fB\fR" 4
.IX Item "Pt"
A text parameter composed of printable characters.
-.SH "Values"
-.IX Header "Values"
+.Sh "Values"
+.IX Subsection "Values"
.ie n .IP "\fB\fB""ENQ""\fB\fR" 4
.el .IP "\fB\f(CBENQ\fB\fR" 4
.IX Item "ENQ"
.el .IP "\fB\f(CBSPC\fB\fR" 4
.IX Item "SPC"
Space Character
-.SH "Escape Sequences"
-.IX Header "Escape Sequences"
+.Sh "Escape Sequences"
+.IX Subsection "Escape Sequences"
.ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4
.el .IP "\fB\f(CBESC # 8\fB\fR" 4
.IX Item "ESC # 8"
.PP
.IX Xref "CSI"
-.SH "CSI (Command Sequence Introducer) Sequences"
-.IX Header "CSI (Command Sequence Introducer) Sequences"
+.Sh "\s-1CSI\s0 (Command Sequence Introducer) Sequences"
+.IX Subsection "CSI (Command Sequence Introducer) Sequences"
.ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4
.el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4
.IX Item "ESC [ Ps @"
.PP
.IX Xref "PrivateModes"
-.SH "DEC Private Modes"
-.IX Header "DEC Private Modes"
+.Sh "\s-1DEC\s0 Private Modes"
+.IX Subsection "DEC Private Modes"
.ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4
.el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4
.IX Item "ESC [ ? Pm h"
.PP
.IX Xref "XTerm"
-.SH "XTerm Operating System Commands"
-.IX Header "XTerm Operating System Commands"
+.Sh "XTerm Operating System Commands"
+.IX Subsection "XTerm Operating System Commands"
.ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4
.el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4
.IX Item "ESC ] Ps;Pt ST"
Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).
.TE
-.PP
-
-.IX Xref "XPM"
.SH "XPM"
.IX Header "XPM"
For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value
by other values to change the degree of opacity. If it doesn't work and
your server crashes, you got to keep the pieces.
-=head3 Why do some chinese characters look so different than others?
-
-This is because there is a difference between script and language --
-rxvt-unicode does not know which language the text that is output is,
-as it only knows the unicode character codes. If rxvt-unicode first
-sees a japanese/chinese character, it might choose a japanese font for
-display. Subsequent japanese characters will use that font. Now, many
-chinese characters aren't represented in japanese fonts, so when the first
-non-japanese character comes up, rxvt-unicode will look for a chinese font
--- unfortunately at this point, it will still use the japanese font for
-chinese characters that are also in the japanese font.
-
-The workaround is easy: just tag a chinese font at the end of your font
-list (see the previous question). The key is to view the font list as
-a preference list: If you expect more japanese, list a japanese font
-first. If you expect more chinese, put a chinese font first.
-
-In the future it might be possible to switch language preferences at
-runtime (the internal data structure has no problem with using different
-fonts for the same character at the same time, but no interface for this
-has been designed yet).
-
-Until then, you might get away with switching fonts at runtime (see L<Can
-I switch the fonts at runtime?> later in this document).
-
=head3 Why does rxvt-unicode sometimes leave pixel droppings?
Most fonts were not designed for terminal use, which means that character
URxvt.color7: #e1dddd
URxvt.color15: #e1dddd
-(They were described (not by me) as "pretty girly").
+They have been described (not by me) as "pretty girly".
=head3 Why do some characters look so much different than others?
-
+
See next entry.
-
+
=head3 How does rxvt-unicode choose fonts?
-
+
Most fonts do not contain the full range of Unicode, which is
fine. Chances are that the font you (or the admin/package maintainer of
your system/os) have specified does not cover all the characters you want
to display.
-
+
B<rxvt-unicode> makes a best-effort try at finding a replacement
font. Often the result is fine, but sometimes the chosen font looks
bad/ugly/wrong. Some fonts have totally strange characters that don't
resemble the correct glyph at all, and rxvt-unicode lacks the artificial
intelligence to detect that a specific glyph is wrong: it has to believe
the font that the characters it claims to contain indeed look correct.
-
+
In that case, select a font of your taste and add it to the font list,
e.g.:
-
+
@@URXVT_NAME@@ -fn basefont,font2,font3...
-
+
When rxvt-unicode sees a character, it will first look at the base
font. If the base font does not contain the character, it will go to the
next font, and so on. Specifying your own fonts will also speed up this
search and use less resources within rxvt-unicode and the X-server.
-
+
The only limitation is that none of the fonts may be larger than the base
font, as the base font defines the terminal character cell size, which
must be the same due to the way terminals work.
+=head3 Why do some chinese characters look so different than others?
+
+This is because there is a difference between script and language --
+rxvt-unicode does not know which language the text that is output is,
+as it only knows the unicode character codes. If rxvt-unicode first
+sees a japanese/chinese character, it might choose a japanese font for
+display. Subsequent japanese characters will use that font. Now, many
+chinese characters aren't represented in japanese fonts, so when the first
+non-japanese character comes up, rxvt-unicode will look for a chinese font
+-- unfortunately at this point, it will still use the japanese font for
+chinese characters that are also in the japanese font.
+
+The workaround is easy: just tag a chinese font at the end of your font
+list (see the previous question). The key is to view the font list as
+a preference list: If you expect more japanese, list a japanese font
+first. If you expect more chinese, put a chinese font first.
+
+In the future it might be possible to switch language preferences at
+runtime (the internal data structure has no problem with using different
+fonts for the same character at the same time, but no interface for this
+has been designed yet).
+
+Until then, you might get away with switching fonts at runtime (see L<Can
+I switch the fonts at runtime?> later in this document).
=head2 Keyboard, Mouse & User Interaction
=head1 RXVT-UNICODE TECHNICAL REFERENCE
-=head1 DESCRIPTION
-
The rest of this document describes various technical aspects of
B<rxvt-unicode>. First the description of supported command sequences,
followed by pixmap support and last by a description of all features
selectable at C<configure> time.
-=head1 Definitions
+=head2 Definitions
=over 4
=back
-=head1 Values
+=head2 Values
=over 4
=back
-=head1 Escape Sequences
+=head2 Escape Sequences
=over 4
X<CSI>
-=head1 CSI (Command Sequence Introducer) Sequences
+=head2 CSI (Command Sequence Introducer) Sequences
=over 4
X<PrivateModes>
-=head1 DEC Private Modes
+=head2 DEC Private Modes
=over 4
X<XTerm>
-=head1 XTerm Operating System Commands
+=head2 XTerm Operating System Commands
=over 4
=back
-X<XPM>
-
=head1 XPM
For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
by other values to change the degree of opacity. If it doesn't work and
your server crashes, you got to keep the pieces.
- Why do some chinese characters look so different than others?
- This is because there is a difference between script and language --
- rxvt-unicode does not know which language the text that is output is, as
- it only knows the unicode character codes. If rxvt-unicode first sees a
- japanese/chinese character, it might choose a japanese font for display.
- Subsequent japanese characters will use that font. Now, many chinese
- characters aren't represented in japanese fonts, so when the first
- non-japanese character comes up, rxvt-unicode will look for a chinese
- font -- unfortunately at this point, it will still use the japanese font
- for chinese characters that are also in the japanese font.
-
- The workaround is easy: just tag a chinese font at the end of your font
- list (see the previous question). The key is to view the font list as a
- preference list: If you expect more japanese, list a japanese font
- first. If you expect more chinese, put a chinese font first.
-
- In the future it might be possible to switch language preferences at
- runtime (the internal data structure has no problem with using different
- fonts for the same character at the same time, but no interface for this
- has been designed yet).
-
- Until then, you might get away with switching fonts at runtime (see "Can
- I switch the fonts at runtime?" later in this document).
-
Why does rxvt-unicode sometimes leave pixel droppings?
Most fonts were not designed for terminal use, which means that
character size varies a lot. A font that is otherwise fine for terminal
URxvt.color7: #e1dddd
URxvt.color15: #e1dddd
- (They were described (not by me) as "pretty girly").
+ They have been described (not by me) as "pretty girly".
Why do some characters look so much different than others?
See next entry.
e.g.:
urxvt -fn basefont,font2,font3...
-
+
When rxvt-unicode sees a character, it will first look at the base font.
If the base font does not contain the character, it will go to the next
font, and so on. Specifying your own fonts will also speed up this
base font, as the base font defines the terminal character cell size,
which must be the same due to the way terminals work.
+ Why do some chinese characters look so different than others?
+ This is because there is a difference between script and language --
+ rxvt-unicode does not know which language the text that is output is, as
+ it only knows the unicode character codes. If rxvt-unicode first sees a
+ japanese/chinese character, it might choose a japanese font for display.
+ Subsequent japanese characters will use that font. Now, many chinese
+ characters aren't represented in japanese fonts, so when the first
+ non-japanese character comes up, rxvt-unicode will look for a chinese
+ font -- unfortunately at this point, it will still use the japanese font
+ for chinese characters that are also in the japanese font.
+
+ The workaround is easy: just tag a chinese font at the end of your font
+ list (see the previous question). The key is to view the font list as a
+ preference list: If you expect more japanese, list a japanese font
+ first. If you expect more chinese, put a chinese font first.
+
+ In the future it might be possible to switch language preferences at
+ runtime (the internal data structure has no problem with using different
+ fonts for the same character at the same time, but no interface for this
+ has been designed yet).
+
+ Until then, you might get away with switching fonts at runtime (see "Can
+ I switch the fonts at runtime?" later in this document).
+
Keyboard, Mouse & User Interaction
The new selection selects pieces that are too big, how can I select single words?
If you want to select e.g. alphanumeric words, you can use the following
likely limited to 8-bit encodings.
RXVT-UNICODE TECHNICAL REFERENCE
-DESCRIPTION
The rest of this document describes various technical aspects of
rxvt-unicode. First the description of supported command sequences,
followed by pixmap support and last by a description of all features
selectable at "configure" time.
-Definitions
+ Definitions
"c" The literal character c.
"C" A single (required) character.
"Pt"
A text parameter composed of printable characters.
-Values
+ Values
"ENQ"
Enquiry (Ctrl-E) = Send Device Attributes (DA) request attributes
from terminal. See "ESC [ Ps c".
"SPC"
Space Character
-Escape Sequences
+ Escape Sequences
"ESC # 8"
DEC Screen Alignment Test (DECALN)
-CSI (Command Sequence Introducer) Sequences
+ CSI (Command Sequence Introducer) Sequences
"ESC [ Ps @"
Insert "Ps" (Blank) Character(s) [default: 1] (ICH)
-DEC Private Modes
+ DEC Private Modes
"ESC [ ? Pm h"
DEC Private Mode Set (DECSET)
-XTerm Operating System Commands
+ XTerm Operating System Commands
"ESC ] Ps;Pt ST"
Set XTerm Parameters. 8-bit ST: 0x9c, 7-bit ST sequence: ESC \
(0x1b, 0x5c), backwards compatible terminator BEL (0x07) is also
Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).
-
-
XPM
For the XPM XTerm escape sequence "ESC ] 20 ; Pt ST" then value of "Pt"
can be the name of the background pixmap followed by a sequence of
projects / dana / urxvt.git / commitdiff