From: root Date: Tue, 31 Jan 2006 21:10:44 +0000 (+0000) Subject: *** empty log message *** X-Git-Url: http://git.openbox.org/?a=commitdiff_plain;h=b9bca17bf35439c38af39926e1b1d85d4ab74a49;p=dana%2Furxvt.git *** empty log message *** --- diff --git a/doc/rxvt.7.html b/doc/rxvt.7.html index 2e073ed1..b133a13e 100644 --- a/doc/rxvt.7.html +++ b/doc/rxvt.7.html @@ -37,7 +37,6 @@
  • Keyboard, Mouse & User Interaction
    • @@ -107,13 +108,16 @@
  • RXVT-UNICODE TECHNICAL REFERENCE
    • -
  • DESCRIPTION
    • -
  • Definitions
    • -
  • Values
    • -
  • Escape Sequences
    • -
  • CSI (Command Sequence Introducer) Sequences
    • -
  • DEC Private Modes
    • -
  • XTerm Operating System Commands
    • + +
  • XPM
  • Mouse Reporting
  • Key Codes
    • @@ -350,27 +354,6 @@ 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 use might @@ -507,44 +490,52 @@ including the murky brown that passes for low-intensity yellow:

    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
+
    See next entry.
    
+
    
+
    
+
    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
+to display.
    
+
    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.:
    +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 -fn basefont,font2,font3...
    -
    -
-When rxvt-unicode sees a character, it will first look at the base
+
    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
+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.
    +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

    @@ -1051,18 +1042,13 @@ 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 >
    @@ -1098,8 +1084,7 @@ A text parameter composed of printable characters.

    -
    -

    Values

    +

    Values

    ENQ >
    @@ -1172,8 +1157,7 @@ Space Character

    -
    -

    Escape Sequences

    +

    Escape Sequences

    ESC # 8 >
    @@ -1316,8 +1300,7 @@ Designate Kanji Character Set

    -
    -

    CSI (Command Sequence Introducer) Sequences

    +

    CSI (Command Sequence Introducer) Sequences

    ESC [ Ps @ >
    @@ -1623,8 +1606,7 @@ Request Terminal Parameters (DECREQTPARM)

    -
    -

    DEC Private Modes

    +

    DEC Private Modes

    ESC [ ? Pm h >
    @@ -1800,8 +1782,7 @@ Enter Tektronix Mode (DECTEK)

    -
    -

    XTerm Operating System Commands

    +

    XTerm Operating System Commands

    ESC ] Ps;Pt ST >
    @@ -1843,7 +1824,6 @@ Set XTerm Parameters. 8-bit ST: 0x9c, 7-bit ST sequence: ESC \ (0x1b, Ps = 721Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). Ps = 777Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).

    -

    @@ -2428,24 +2408,18 @@ Use the X Window System (pretty much default, eh?).
    Look for the XPM includes in DIR. - -

    --with-xpm-library=DIR
    Look for the XPM library in DIR. - -

    --with-xpm
    Not needed - define via --enable-xpm-background. - -

    @@ -2455,9 +2429,7 @@ Not needed - define via --enable-xpm-background.

    Marc Lehmann <rxvt@schmorp.de> converted this document to pod and reworked it from the original Rxvt documentation, which was done by Geoff Wing <gcw@pobox.com>, who in turn used the XTerm documentation and other -sources. - -

    +sources.