/[gentoo]/xml/htdocs/doc/en/utf-8.xml
Gentoo

Diff of /xml/htdocs/doc/en/utf-8.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.4 Revision 1.5
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/utf-8.xml,v 1.4 2005/02/23 20:20:24 so Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/utf-8.xml,v 1.5 2005/02/24 14:57:18 cam Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/doc/en/utf-8.xml"> 5<guide link="/doc/en/utf-8.xml">
6<title>Using UTF-8 with Gentoo</title> 6<title>Using UTF-8 with Gentoo</title>
7 7
18specifically UTF-8. 18specifically UTF-8.
19</abstract> 19</abstract>
20 20
21<license /> 21<license />
22 22
23<version>1.3</version> 23<version>1.4</version>
24<date>2005-02-23</date> 24<date>2005-02-23</date>
25 25
26<chapter> 26<chapter>
27<title>Character Encodings</title> 27<title>Character Encodings</title>
28<section> 28<section>
459 459
460<p> 460<p>
461Terminal emulators that use Xft and support Unicode are harder to come by. 461Terminal emulators that use Xft and support Unicode are harder to come by.
462Aside from Konsole and gnome-terminal, the best options in Portage are 462Aside from Konsole and gnome-terminal, the best options in Portage are
463<c>x11-terms/rxvt-unicode</c>, <c>xfce-extra/terminal</c>, 463<c>x11-terms/rxvt-unicode</c>, <c>xfce-extra/terminal</c>,
464<c>app-gnustep/terminal</c>, <c>x11-terms/mlterm</c>, <c>x11-terms/mrxvt</c> or 464<c>gnustep-apps/terminal</c>, <c>x11-terms/mlterm</c>, <c>x11-terms/mrxvt</c> or
465plain <c>x11-terms/xterm</c> when built with the <c>unicode</c> USE flag and 465plain <c>x11-terms/xterm</c> when built with the <c>unicode</c> USE flag and
466invoked as <c>uxterm</c>. <c>app-misc/screen</c> supports UTF-8 too, when 466invoked as <c>uxterm</c>. <c>app-misc/screen</c> supports UTF-8 too, when
467invoked as <c>screen -u</c> or the following is put into the 467invoked as <c>screen -u</c> or the following is put into the
468<path>~/.screenrc</path>: 468<path>~/.screenrc</path>:
469</p> 469</p>
512<section> 512<section>
513<title>Irssi</title> 513<title>Irssi</title>
514<body> 514<body>
515 515
516<p> 516<p>
517Irssi has complete UTF-8 support, although it does require a user to set an 517Since 0.8.10, Irssi has complete UTF-8 support, although it does require a user
518option. 518to set an option.
519</p> 519</p>
520 520
521<pre caption="Enabling UTF-8 in Irssi"> 521<pre caption="Enabling UTF-8 in Irssi">
522/set term_charset UTF-8 522/set term_charset UTF-8
523</pre> 523</pre>
524
525<impo>
526The <c>/recode</c> command is only available on irssi-0.8.10 and above.
527</impo>
528 524
529<p> 525<p>
530For channels where non-ASCII characters are often exchanged in non-UTF-8 526For channels where non-ASCII characters are often exchanged in non-UTF-8
531charsets, the <c>/recode</c> command may be used to convert the characters. 527charsets, the <c>/recode</c> command may be used to convert the characters.
532Type <c>/help recode</c> for more information. 528Type <c>/help recode</c> for more information.

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.5

  ViewVC Help
Powered by ViewVC 1.1.20