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

Comparing rxvt-unicode/doc/rxvt.7.html (file contents):
Revision 1.18 by root, Mon Feb 21 19:26:06 2005 UTC vs.
Revision 1.19 by root, Sun Apr 17 22:36:13 2005 UTC

… …
438<p>As you might have guessed, FreeBSD does neither define this symobl nor 438<p>As you might have guessed, FreeBSD does neither define this symobl nor
439does it support it. Instead, it uses it's own internal representation of 439does it support it. Instead, it uses it's own internal representation of
440<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p> 440<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p>
441</dd> 441</dd>
442<dd> 442<dd>
443<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and
444<code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p>
445</dd>
446<dd>
443<p>However, <code>__STDC_ISO_10646__</code> is the only sane way to support 447<p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language
444multi-language apps in an OS, as using a locale-dependent (and 448apps in an OS, as using a locale-dependent (and non-standardized)
445non-standardized) representation of <strong>wchar_t</strong> makes it impossible to 449representation of <strong>wchar_t</strong> makes it impossible to convert between
446convert between <strong>wchar_t</strong> (as used by X11 and your applications) and any 450<strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding
447other encoding without implementing OS-specific-wrappers for each and 451without implementing OS-specific-wrappers for each and every locale. There
448every locale. There simply are no APIs to convert <strong>wchar_t</strong> into anything 452simply are no APIs to convert <strong>wchar_t</strong> into anything except the current
449except the current locale encoding.</p> 453locale encoding.</p>
450</dd> 454</dd>
451<dd> 455<dd>
452<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this 456<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this
453by carrying their own replacement functions for character set handling 457by carrying their own replacement functions for character set handling
454with them, and either implementing OS-dependent hacks or doing multiple 458with them, and either implementing OS-dependent hacks or doing multiple
… …
2529</dd> 2533</dd>
2530<p></p> 2534<p></p>
2531<dt><strong><a name="item__2d_2dwith_2dcodesets_3dname_2c_2e_2e_2e">--with-codesets=NAME,...</a></strong><br /> 2535<dt><strong><a name="item__2d_2dwith_2dcodesets_3dname_2c_2e_2e_2e">--with-codesets=NAME,...</a></strong><br />
2532</dt> 2536</dt>
2533<dd> 2537<dd>
2534Compile in support for additional codeset (encoding) groups (eu, vn are 2538Compile in support for additional codeset (encoding) groups (<code>eu</code>, <code>vn</code>
2535always compiled in, which includes most 8-bit character sets). These 2539are always compiled in, which includes most 8-bit character sets). These
2536codeset tables are currently only used for driving X11 core fonts, they 2540codeset tables are used for driving X11 core fonts, they are not required
2537are not required for Xft fonts. Compiling them in will make your binary 2541for Xft fonts, although having them compiled in lets rxvt-unicode choose
2538bigger (together about 700kB), but it doesn't increase memory usage unless 2542replacement fonts more intelligently. Compiling them in will make your
2543binary bigger (all of together cost about 700kB), but it doesn't increase
2539you use an X11 font requiring one of these encodings. 2544memory usage unless you use a font requiring one of these encodings.
2540</dd> 2545</dd>
2541<table> 2546<table>
2542<tr><td>all</td><td>all available codeset groups</td></tr> 2547<tr><td>all</td><td>all available codeset groups</td></tr>
2543<tr><td>zh</td><td>common chinese encodings</td></tr> 2548<tr><td>zh</td><td>common chinese encodings</td></tr>
2544<tr><td>zh_ext</td><td>rarely used but very big chinese encodigs</td></tr> 2549<tr><td>zh_ext</td><td>rarely used but very big chinese encodigs</td></tr>
… …
2783 backindex and forwardindex escape sequence 2788 backindex and forwardindex escape sequence
2784 window op and some xterm/OSC escape sequences 2789 window op and some xterm/OSC escape sequences
2785 tripleclickwords 2790 tripleclickwords
2786 settable insecure mode 2791 settable insecure mode
2787 keysym remapping support 2792 keysym remapping support
2793 cursor blinking and underline cursor
2788 -embed and -pty-fd options</pre> 2794 -embed and -pty-fd options</pre>
2789</dd> 2795</dd>
2790<p></p> 2796<p></p>
2791<dt><strong><a name="item__2d_2denable_2diso14755">--enable-iso14755</a></strong><br /> 2797<dt><strong><a name="item__2d_2denable_2diso14755">--enable-iso14755</a></strong><br />
2792</dt> 2798</dt>
… …
2848</dt> 2854</dt>
2849<dd> 2855<dd>
2850Add smart growth/shrink behaviour when changing font size via from hot 2856Add smart growth/shrink behaviour when changing font size via from hot
2851keys. This should keep in a fixed position the rxvt corner which is 2857keys. This should keep in a fixed position the rxvt corner which is
2852closest to a corner of the screen. 2858closest to a corner of the screen.
2853</dd>
2854<p></p>
2855<dt><strong><a name="item__2d_2denable_2dcursor_2dblink">--enable-cursor-blink</a></strong><br />
2856</dt>
2857<dd>
2858Add support for a blinking cursor.
2859</dd> 2859</dd>
2860<p></p> 2860<p></p>
2861<dt><strong><a name="item__2d_2denable_2dpointer_2dblank">--enable-pointer-blank</a></strong><br /> 2861<dt><strong><a name="item__2d_2denable_2dpointer_2dblank">--enable-pointer-blank</a></strong><br />
2862</dt> 2862</dt>
2863<dd> 2863<dd>

Diff Legend

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