| 1 | <?xml version='1.0' encoding="UTF-8"?> |
1 | <?xml version='1.0' encoding="UTF-8"?> |
| 2 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
2 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 3 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/utf-8.xml,v 1.57 2012/07/24 12:12:51 swift Exp $ --> |
3 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/utf-8.xml,v 1.58 2012/12/30 01:48:51 nightmorph Exp $ --> |
| 4 | |
4 | |
| 5 | <guide> |
5 | <guide> |
| 6 | <title>Using UTF-8 with Gentoo</title> |
6 | <title>Using UTF-8 with Gentoo</title> |
| 7 | |
7 | |
| 8 | <author title="Author"> |
8 | <author title="Author"> |
| 9 | <mail link="slarti@gentoo.org">Thomas Martin</mail> |
9 | <mail link="slarti@gentoo.org">Thomas Martin</mail> |
| 10 | </author> |
10 | </author> |
| 11 | <author title="Contributor"> |
11 | <author title="Contributor"> |
| 12 | <mail link="devil@gentoo.org.ua">Alexander Simonov</mail> |
12 | <mail link="devil@gentoo.org.ua">Alexander Simonov</mail> |
| 13 | </author> |
13 | </author> |
| 14 | <author title="Editor"> |
14 | <author title="Editor"> |
| 15 | <mail link="fox2mike@gentoo.org">Shyam Mani</mail> |
15 | <mail link="fox2mike@gentoo.org">Shyam Mani</mail> |
| 16 | </author> |
16 | </author> |
| 17 | <author title="Editor"> |
17 | <author title="Editor"> |
| 18 | <mail link="nightmorph"/> |
18 | <mail link="nightmorph"/> |
| 19 | </author> |
19 | </author> |
| 20 | |
20 | |
| 21 | <abstract> |
21 | <abstract> |
| 22 | This guide shows you how to set up and use the UTF-8 Unicode character set with |
22 | This guide shows you how to set up and use the UTF-8 Unicode character set with |
| 23 | your Gentoo Linux system, after explaining the benefits of Unicode and more |
23 | your Gentoo Linux system, after explaining the benefits of Unicode and more |
| 24 | specifically UTF-8. |
24 | specifically UTF-8. |
| 25 | </abstract> |
25 | </abstract> |
| 26 | |
26 | |
| 27 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
27 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
| 28 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
28 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 29 | <license /> |
29 | <license /> |
| 30 | |
30 | |
| 31 | <version>6</version> |
31 | <version>7</version> |
| 32 | <date>2012-07-24</date> |
32 | <date>2012-12-29</date> |
| 33 | |
33 | |
| 34 | <chapter> |
34 | <chapter> |
| 35 | <title>Character Encodings</title> |
35 | <title>Character Encodings</title> |
| 36 | <section> |
36 | <section> |
| 37 | <title>What is a Character Encoding?</title> |
37 | <title>What is a Character Encoding?</title> |
| 38 | <body> |
38 | <body> |
| 39 | |
39 | |
| 40 | <p> |
40 | <p> |
| 41 | Computers do not understand text themselves. Instead, every character is |
41 | Computers do not understand text themselves. Instead, every character is |
| 42 | represented by a number. Traditionally, each set of numbers used to represent |
42 | represented by a number. Traditionally, each set of numbers used to represent |
| 43 | alphabets and characters (known as a coding system, encoding or character set) |
43 | alphabets and characters (known as a coding system, encoding or character set) |
| 44 | was limited in size due to limitations in computer hardware. |
44 | was limited in size due to limitations in computer hardware. |
| 45 | </p> |
45 | </p> |
| 46 | |
46 | |
| 47 | </body> |
47 | </body> |
| … | |
… | |
| 529 | </section> |
529 | </section> |
| 530 | <section> |
530 | <section> |
| 531 | <title>Window Managers and Terminal Emulators</title> |
531 | <title>Window Managers and Terminal Emulators</title> |
| 532 | <body> |
532 | <body> |
| 533 | |
533 | |
| 534 | <p> |
534 | <p> |
| 535 | Window managers not built on GTK or Qt generally have very good Unicode |
535 | Window managers not built on GTK or Qt generally have very good Unicode |
| 536 | support, as they often use the Xft library for handling fonts. If your window |
536 | support, as they often use the Xft library for handling fonts. If your window |
| 537 | manager does not use Xft for fonts, you can still use the FontSpec mentioned in |
537 | manager does not use Xft for fonts, you can still use the FontSpec mentioned in |
| 538 | the previous section as a Unicode font. |
538 | the previous section as a Unicode font. |
| 539 | </p> |
539 | </p> |
| 540 | |
540 | |
| 541 | <p> |
541 | <p> |
| 542 | Terminal emulators that use Xft and support Unicode are harder to come by. |
542 | Terminal emulators that use Xft and support Unicode are harder to come by. |
| 543 | Aside from Konsole and gnome-terminal, the best options in Portage are |
543 | Aside from Konsole and gnome-terminal, the best options in Portage are |
| 544 | <c>x11-terms/rxvt-unicode</c>, <c>x11-terms/terminal</c>, |
544 | <c>x11-terms/rxvt-unicode</c>, <c>x11-terms/xfce4-terminal</c>, |
| 545 | <c>gnustep-apps/terminal</c>, <c>x11-terms/mlterm</c>, or plain |
545 | <c>gnustep-apps/terminal</c>, <c>x11-terms/mlterm</c>, or plain |
| 546 | <c>x11-terms/xterm</c> when built with the <c>unicode</c> USE flag and invoked |
546 | <c>x11-terms/xterm</c> when built with the <c>unicode</c> USE flag and invoked |
| 547 | as <c>uxterm</c>. <c>app-misc/screen</c> supports UTF-8 too, when invoked as |
547 | as <c>uxterm</c>. <c>app-misc/screen</c> supports UTF-8 too, when invoked as |
| 548 | <c>screen -U</c> or the following is put into the <path>~/.screenrc</path>: |
548 | <c>screen -U</c> or the following is put into the <path>~/.screenrc</path>: |
| 549 | </p> |
549 | </p> |
| 550 | |
550 | |
| 551 | <pre caption="~/.screenrc for UTF-8"> |
551 | <pre caption="~/.screenrc for UTF-8"> |
| 552 | defutf8 on |
552 | defutf8 on |
| 553 | </pre> |
553 | </pre> |
| 554 | |
554 | |
| 555 | </body> |
555 | </body> |
| 556 | </section> |
556 | </section> |
| 557 | <section> |
557 | <section> |
| 558 | <title>Vim, Emacs, Xemacs and Nano</title> |
558 | <title>Vim, Emacs, Xemacs and Nano</title> |
| 559 | <body> |
559 | <body> |
Parent Directory
| 
Revision Log
| 
Patch