/[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.19 Revision 1.20
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.19 2005/06/18 03:53:44 fox2mike Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/utf-8.xml,v 1.20 2005/06/20 11:23:58 fox2mike 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
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">
15 <mail link="fox2mike@gentoo.org">Shyam Mani</mail>
16</author>
14 17
15<abstract> 18<abstract>
16This guide shows you how to set up and use the UTF-8 Unicode character set with 19This guide shows you how to set up and use the UTF-8 Unicode character set with
17your Gentoo Linux system, after explaining the benefits of Unicode and more 20your Gentoo Linux system, after explaining the benefits of Unicode and more
18specifically UTF-8. 21specifically UTF-8.
19</abstract> 22</abstract>
20 23
24<!-- The content of this document is licensed under the CC-BY-SA license -->
25<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
21<license /> 26<license />
22 27
23<version>2.2</version> 28<version>2.3</version>
24<date>2005-06-18</date> 29<date>2005-06-20</date>
25 30
26<chapter> 31<chapter>
27<title>Character Encodings</title> 32<title>Character Encodings</title>
28<section> 33<section>
29<title>What is a Character Encoding?</title> 34<title>What is a Character Encoding?</title>
30<body> 35<body>
31 36
32<p> 37<p>
33Computers do not understand text themselves. Instead, every character is 38Computers do not understand text themselves. Instead, every character is
34represented by a number. Traditionally, each set of numbers used to represent 39represented by a number. Traditionally, each set of numbers used to represent
35alphabets and characters (known as a coding system, encoding or character set) 40alphabets and characters (known as a coding system, encoding or character set)
36was limited in size due to limitations in computer hardware. 41was limited in size due to limitations in computer hardware.
37</p> 42</p>
38 43
39</body> 44</body>
631<section> 636<section>
632<title>Man</title> 637<title>Man</title>
633<body> 638<body>
634 639
635<p> 640<p>
636Man pages are an integral part of any Linux machine. To ensure that any 641Man pages are an integral part of any Linux machine. To ensure that any
637unicode in your man pages render correctly, edit <path>/etc/man.conf</path> 642unicode in your man pages render correctly, edit <path>/etc/man.conf</path>
638and replace a line as shown below. 643and replace a line as shown below.
639</p> 644</p>
640 645
641<pre caption="man.conf changes for Unicode support"> 646<pre caption="man.conf changes for Unicode support">
642<comment>(This is the old line)</comment> 647<comment>(This is the old line)</comment>
643NROFF /usr/bin/nroff -Tascii -c -mandoc 648NROFF /usr/bin/nroff -Tascii -c -mandoc
644<comment>(Replace the one above with this)</comment> 649<comment>(Replace the one above with this)</comment>
645NROFF /usr/bin/nroff -mandoc -c 650NROFF /usr/bin/nroff -mandoc -c
651</pre>
652
653</body>
654</section>
655<section>
656<title>elinks and links</title>
657<body>
658
659<p>
660These are commonly used text-based browsers, and we shall see how we can enable
661UTF-8 support on them. On <c>elinks</c> and <c>links</c>, there are two ways to
662go about this, one using the Setup option from within the browser or editing the
663config file. To set the option through the browser, open a site with
664<c>elinks</c> or <c>links</c> and then <c>Alt+S</c> to enter the Setup Menu then
665select Terminal options, or press <c>T</c>. Scroll down and select the last
666option <c>UTF-8 I/O</c> by pressing Enter. Then Save and exit the menu. On
667<c>links</c> you may have to do a repeat <c>Alt+S</c> and then press <c>S</c> to
668save. The config file option, is shown below.
669</p>
670
671<pre caption="Enabling UTF-8 for elinks/links">
672<comment>(For elinks, edit /etc/elinks/elinks.conf or ~/.elinks/elinks.conf and
673add the following line)</comment>
674set terminal.linux.utf_8_io = 1
675
676<comment>(For links, edit ~/.links/links.cfg and add the following
677line)</comment>
678terminal "xterm" 0 1 0 us-ascii utf-8
646</pre> 679</pre>
647 680
648</body> 681</body>
649</section> 682</section>
650<section> 683<section>
651<title>Testing it all out</title> 684<title>Testing it all out</title>
652<body> 685<body>
653 686
654<p> 687<p>
655There are numerous UTF-8 test websites around. <c>net-www/w3m</c>, 688There are numerous UTF-8 test websites around. <c>net-www/w3m</c>,
656<c>net-www/links</c>, <c>net-www/elinks</c>, <c>net-www/lynx</c> and all 689<c>net-www/links</c>, <c>net-www/elinks</c>, <c>net-www/lynx</c> and all
657Mozilla based browsers (including Firefox) support UTF-8. Konqueror and Opera 690Mozilla based browsers (including Firefox) support UTF-8. Konqueror and Opera
658have full UTF-8 support too. 691have full UTF-8 support too.
659</p> 692</p>
660 693

Legend:
Removed from v.1.19  
changed lines
  Added in v.1.20

  ViewVC Help
Powered by ViewVC 1.1.20