Penguin
Recent Changes
Blame: vt-is-UTF8(1)
EditPageHistoryDiffInfoLikePages
Annotated edit history of vt-is-UTF8(1) version 4, including all changes. View license author blame.
Rev Author # Line
1 perry 1 VT-IS-UTF8
2 !!!VT-IS-UTF8
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 OPTIONS
7 BUGS
8 SEE ALSO
9 ----
10 !!NAME
11
12
13 vt-is-UTF8 - check whether current VT is in UTF8- or byte-mode.
14 !!SYNOPSIS
15
16
17 __vt-is-UTF8 [[__''-h''__|__''--help''__]
18 [[__''-V''__|__''--version''__]
19 [[__''-q''__|__''--quiet''__]__
20 !!DESCRIPTION
21
22
23 __vt-is-UTF8__ checks whether the current VT is in UTF8
24 mode, by writing (and erasing afterwards) a 3-byte-long UTF8
25 sequence, and looking how much chars where displayed by the
26 console driver.
27
28
29 A message telling in which mode the console is is then
30 written to stdout (except if the ''--quiet'' option was
31 given).
32
33
34 If the ''--quiet'' option is not given, the value
35 returned is 1 if an error occurs, else 0.
36 !!OPTIONS
37
38
39 ''-h --help''
40
41
42 display version number, a short help message and
43 exit.
44
45
46 ''-V --version''
47
48
49 display version number and exit.
50
51
52 ''-q --quiet''
53
54
55 do not print on stdout in with mode we are, but return the
56 state as exit-status 1 if in UTF8-mode, 0 if in byte-mode.
57 In case of error, 0 is returned and a message is displayed
58 on stderr.
59 !!BUGS
60
61
62 The check should be done by directly asking the kernel,
63 which is not possible as of kernels 2.0.x.
64
65
66 As of kernel 2.0.35, the byte-mode is sometimes erroneously
67 detected as UTF8-mode, after switching from a 512-chars font
68 to a 256-chars font. This is probably a console-driver
69 bug.
70 !!SEE ALSO
71
72
4 perry 73 unicode_start(1),
74 unicode_stop(1).
1 perry 75 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.