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
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
|
* Immediate
** showfont.1 was not renamed to showcfont.1
* General:
** investigate why underlining gives strange results after changing
from eg. iso01.f08 to iso01.f14. Maybe setfont should set correct
underlining pos when changing char height ? (see debian bug #8949 -
SVGATextMode handles this correctly) - see SVGA book.
** bold attribute is told to disappear with 512-chars fonts (debian #8949)
* kernel-level:
** Security:
*** Any user can mess up the keyboard. Only root should be allowed to change
the "basics" of the keytable, ie. minimal subset of ASCII allowing to use
the console and eventually load a new kmap. Then every user could choose
his prefered bells and whistles (when each VT would get its kmap).
*** Any user can mess up the display (font/SFM). Normal users should be
allowed at most to change something about chars not mapped-to by an ASCII
char (U+0000-U+008F).
*** Any user can choose/mess up the ACM. It should be restored on logout, and
maybe get the same kind of protection than described for font/SFM.
** Unicode support:
*** It seems there is some bad interaction between 512-chars mode and
UTF. It seems that after going into 512-chars mode, and then back
into 256-chars mode, the mechanism used by vt-is-utf8 does not work.
*** The kernel currently considers an empty SFM as valid. This should not
be, as then ACM should be restricted to the straight-to-font zone, as when
it's not valid.
*** Current keyboard driver can only handle unicodes up to U+0FFF (uses
0xF000 as a mask to recognize unicode). Current `loadkeys' relies on this.
*** Current keyboard driver outputs UTF8 even when in ASCII mode.
*** Investigate whether it's normal that PIO_UNIMAP doesn't output what
GIO_UNIMAP has set. A diff between [a unimap produced by
psfadtable/psfgettable from iso01.uni] and [a unimap produced by
psfadtable/setfont -opu/psfgettable from iso01.uni] (kernel 2.0.30 / kbd
0.94) shows that mappings have disappeared:
$ setfont iso01-08 && setfont -op iso01-08.psf
$ psfaddtable iso01-08.psf /usr/share/consoletrans/iso01.uni iso01-08a.psf
$ diff <(psfgettable iso01-08a.psf ) <(setfont iso01-08a.psf && setfont -opu >(psfgettable -))
2c2
< # Character table extracted from font iso01-08a.psf
---
> # Character table extracted from font stdin
24,25c24,25
< 0x14 U+00b6
< 0x15 U+00a7
---
> 0x14
> 0x15
** Virtual terminals:
*** VT_OPENQRY doesn't seem to return current VT when it is active, even if it
has no process attached (see VT_IS_IN_USE()/VT_BUSY()).
*** VT's are sometimes (when ?!) considered busy even when not busy (probably
associated to "kbrequest" - also found when a bg process (eg. gpm) has been
associated to this VT, even if it has been killed now)
* tools-level:
** provided fonts:
*** should be shipped in diffable source format.
*** all of them should have a visible replacement char, as lat*.psf do.
*** should be converted to XPSF when it's out.
*** iso07.f08 is wrong (doesn't match the encoding of .f14 and .f16)
** vt-is-UTF8(1)
*** fails when called from mc ?
** libs:
*** findfile() sometimes leaves a zombie (lost SIGCHILD ?). That was
turned around by the maybekillzombie(), but has to be investigated
one day.
*** many functions use fprintf(), which can modify errno, before returning -1.
*** xfseek() should be reworked to not use ftell(). Use a XFILE structure to
manually keep track of the position.
** font-file tools:
*** <priority very_low> Fix codepage's use of getopt() ? (is it really worth ?)
** General:
*** Grep for "#warning", "FIXME" and "UNTESTED" in the source files.
*** Make sure everything is byteorder-independant when reading from/writing to
files. Maybe provide unicode_{read,write}() functions in libcfont.
* FAQ
** Replace references to spawn_login by init/kb (switch priorities)
** 12.M should refer to [latin1]{inputenc} instead.
|