File: c_describe.so

package info (click to toggle)
lookup 1.08b-16
  • links: PTS
  • area: main
  • in suites: forky, sid
  • size: 1,792 kB
  • sloc: ansic: 12,639; makefile: 247; perl: 174; sh: 53
file content (44 lines) | stat: -rw-r--r-- 1,247 bytes parent folder | download | duplicates (9)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
.TP
describe \fIspecifier\fP
This command will tell you how a character (or each character in a string)
is encoded in the various encoding methods:

.nf

    lookup command>  describe ""
    ȵas  EUC  is 0xb5a4 (181 164; \265 \\244)
          as  JIS  is 0x3524 ( 53  36; \065 \\044 "5$")
          as KUTEN is   2104 ( 0x1504; \025 \\004)
          as S-JIS is 0x8b1f (139  31; \213 \\037)
.fi

The quotes surrounding the character or string to describe are optional. 
You can also give a regular ASCII character and have the double-width
version of the character described.... indicating\c
.Q A ", "
for example, would describe\c
.Q  ".  "

.I Specifier
can also be a four-digit kuten value, in which case the character with that
kuten will be described.

If a four-digit
.I specifier
has a hex digit in it, or if it is preceded by\c
.Q 0x ", "
the value is taken as a JIS code. You can precede the value by\c
.Q jis ,\c
.Q sjis ,\c
.Q euc ", "
or\c
.Q kuten
to force interpretation to the requested code.

Finally,
.I specifier
can be a string of stripped JIS (JIS w/o the kanji-in and kanji-out codes,
or with the codes but without the escape characters in them).
For example\c
.Q "F|K\e"
would describe the two characters  and .