1 |
1625 |
jcastillo |
The Linux kernel code has been rewritten to use Unicode to map
|
2 |
|
|
characters to fonts. By downloading a single Unicode-to-font table,
|
3 |
|
|
both the eight-bit character sets and UTF-8 mode are changed to use
|
4 |
|
|
the font as indicated.
|
5 |
|
|
|
6 |
|
|
This changes the semantics of the eight-bit character tables subtly.
|
7 |
|
|
The four character tables are now:
|
8 |
|
|
|
9 |
|
|
Map symbol Map name Escape code (G0)
|
10 |
|
|
|
11 |
|
|
LAT1_MAP Latin-1 (ISO 8859-1) ESC ( B
|
12 |
|
|
GRAF_MAP DEC VT100 pseudographics ESC ( 0
|
13 |
|
|
IBMPC_MAP IBM code page 437 ESC ( U
|
14 |
|
|
USER_MAP User defined ESC ( K
|
15 |
|
|
|
16 |
|
|
In particular, ESC ( U is no longer "straight to font", since the font
|
17 |
|
|
might be completely different than the IBM character set. This
|
18 |
|
|
permits for example the use of block graphics even with a Latin-1 font
|
19 |
|
|
loaded.
|
20 |
|
|
|
21 |
|
|
In accordance with the Unicode standard/ISO 10646 the range U+F000 to
|
22 |
|
|
U+F8FF has been reserved for OS-wide allocation (the Unicode Standard
|
23 |
|
|
refers to this as a "Corporate Zone", since this is inaccurate for
|
24 |
|
|
Linux we call it the "Linux Zone"). U+F000 was picked as the starting
|
25 |
|
|
point since it lets the direct-mapping area start on a large power of
|
26 |
|
|
two (in case 1024- or 2048-character fonts ever become necessary).
|
27 |
|
|
This leaves U+E000 to U+EFFF as End User Zone.
|
28 |
|
|
|
29 |
|
|
The Unicodes in the range U+F000 to U+F1FF have been hard-coded to map
|
30 |
|
|
directly to the loaded font, bypassing the translation table. The
|
31 |
|
|
user-defined map now defaults to U+F000 to U+F1FF, emulating the
|
32 |
|
|
previous behaviour. This range may expand in the future should it be
|
33 |
|
|
warranted.
|
34 |
|
|
|
35 |
|
|
Actual characters assigned in the Linux Zone
|
36 |
|
|
--------------------------------------------
|
37 |
|
|
|
38 |
|
|
In addition, the following characters not present in Unicode 1.1.4 (at
|
39 |
|
|
least, I have not found them!) have been defined; these are used by
|
40 |
|
|
the DEC VT graphics map:
|
41 |
|
|
|
42 |
|
|
U+F800 DEC VT GRAPHICS HORIZONTAL LINE SCAN 1
|
43 |
|
|
U+F801 DEC VT GRAPHICS HORIZONTAL LINE SCAN 3
|
44 |
|
|
U+F803 DEC VT GRAPHICS HORIZONTAL LINE SCAN 7
|
45 |
|
|
U+F804 DEC VT GRAPHICS HORIZONTAL LINE SCAN 9
|
46 |
|
|
|
47 |
|
|
The DEC VT220 uses a 6x10 character matrix, and these characters form
|
48 |
|
|
a smooth progression in the DEC VT graphics character set. I have
|
49 |
|
|
omitted the scan 5 line, since it is also used as a block-graphics
|
50 |
|
|
character, and hence has been coded as U+2500 FORMS LIGHT HORIZONTAL.
|
51 |
|
|
However, I left U+F802 blank should the need arise.
|
52 |
|
|
|
53 |
|
|
Klingon language support
|
54 |
|
|
------------------------
|
55 |
|
|
|
56 |
|
|
Unfortunately, Unicode/ISO 10646 does not allocate code points for the
|
57 |
|
|
language Klingon, probably fearing the potential code point explosion
|
58 |
|
|
if many fictional languages were submitted for inclusion. There are
|
59 |
|
|
also political reasons (the Japanese, for example, are not too happy
|
60 |
|
|
about the whole 16-bit concept to begin with.) However, with Linux
|
61 |
|
|
being a hacker-driven OS it seems this is a brilliant linguistic hack
|
62 |
|
|
worth supporting. Hence I have chosen to add it to the list in the
|
63 |
|
|
Linux Zone.
|
64 |
|
|
|
65 |
|
|
Several glyph forms for the Klingon alphabet has been proposed.
|
66 |
|
|
However, since the set of symbols appear to be consistent throughout,
|
67 |
|
|
with only the actual shapes being different, in keeping with standard
|
68 |
|
|
Unicode practice these differences are considered font variants.
|
69 |
|
|
|
70 |
|
|
Klingon has an alphabet of 26 characters, a positional numeric writing
|
71 |
|
|
system with 10 digits, and is written left-to-right, top-to-bottom.
|
72 |
|
|
Punctuation appears to be only used in Latin transliteration; it is
|
73 |
|
|
appears customary to write each sentence on its own line, and
|
74 |
|
|
centered. Space has been reserved for punctuation should it prove
|
75 |
|
|
necessary.
|
76 |
|
|
|
77 |
|
|
This encoding has been endorsed by the Klingon Language Institute.
|
78 |
|
|
For more information, contact them at:
|
79 |
|
|
|
80 |
|
|
http://www.kli.org/
|
81 |
|
|
|
82 |
|
|
Since the characters in the beginning of the Linux CZ have been more
|
83 |
|
|
of the dingbats/symbols/forms type and this is a language, I have
|
84 |
|
|
located it at the end, on a 16-cell boundary in keeping with standard
|
85 |
|
|
Unicode practice.
|
86 |
|
|
|
87 |
|
|
U+F8D0 KLINGON LETTER A
|
88 |
|
|
U+F8D1 KLINGON LETTER B
|
89 |
|
|
U+F8D2 KLINGON LETTER CH
|
90 |
|
|
U+F8D3 KLINGON LETTER D
|
91 |
|
|
U+F8D4 KLINGON LETTER E
|
92 |
|
|
U+F8D5 KLINGON LETTER GH
|
93 |
|
|
U+F8D6 KLINGON LETTER H
|
94 |
|
|
U+F8D7 KLINGON LETTER I
|
95 |
|
|
U+F8D8 KLINGON LETTER J
|
96 |
|
|
U+F8D9 KLINGON LETTER L
|
97 |
|
|
U+F8DA KLINGON LETTER M
|
98 |
|
|
U+F8DB KLINGON LETTER N
|
99 |
|
|
U+F8DC KLINGON LETTER NG
|
100 |
|
|
U+F8DD KLINGON LETTER O
|
101 |
|
|
U+F8DE KLINGON LETTER P
|
102 |
|
|
U+F8DF KLINGON LETTER Q
|
103 |
|
|
- Written in standard Okrand Latin transliteration
|
104 |
|
|
U+F8E0 KLINGON LETTER QH
|
105 |
|
|
- Written in standard Okrand Latin transliteration
|
106 |
|
|
U+F8E1 KLINGON LETTER R
|
107 |
|
|
U+F8E2 KLINGON LETTER S
|
108 |
|
|
U+F8E3 KLINGON LETTER T
|
109 |
|
|
U+F8E4 KLINGON LETTER TLH
|
110 |
|
|
U+F8E5 KLINGON LETTER U
|
111 |
|
|
U+F8E6 KLINGON LETTER V
|
112 |
|
|
U+F8E7 KLINGON LETTER W
|
113 |
|
|
U+F8E8 KLINGON LETTER Y
|
114 |
|
|
U+F8E9 KLINGON LETTER GLOTTAL STOP
|
115 |
|
|
|
116 |
|
|
U+F8F0 KLINGON DIGIT ZERO
|
117 |
|
|
U+F8F1 KLINGON DIGIT ONE
|
118 |
|
|
U+F8F2 KLINGON DIGIT TWO
|
119 |
|
|
U+F8F3 KLINGON DIGIT THREE
|
120 |
|
|
U+F8F4 KLINGON DIGIT FOUR
|
121 |
|
|
U+F8F5 KLINGON DIGIT FIVE
|
122 |
|
|
U+F8F6 KLINGON DIGIT SIX
|
123 |
|
|
U+F8F7 KLINGON DIGIT SEVEN
|
124 |
|
|
U+F8F8 KLINGON DIGIT EIGHT
|
125 |
|
|
U+F8F9 KLINGON DIGIT NINE
|
126 |
|
|
|
127 |
|
|
Other Fictional and Artificial Scripts
|
128 |
|
|
--------------------------------------
|
129 |
|
|
|
130 |
|
|
Since the assignment of the Klingon Linux Unicode block, a registry of
|
131 |
|
|
fictional and artificial scripts has been established by John Cowan,
|
132 |
|
|
. The ConScript Unicode Registry is accessible at
|
133 |
|
|
http://locke.ccil.org/~cowan/csur/; the ranges used fall at the bottom
|
134 |
|
|
of the End User Zone and can hence not be normatively assigned, but it
|
135 |
|
|
is recommended that people who wish to encode fictional scripts use
|
136 |
|
|
these codes, in the interest of interoperability. For Klingon, CSUR
|
137 |
|
|
has adopted the Linux encoding.
|
138 |
|
|
|
139 |
|
|
H. Peter Anvin
|