blob: 019d12f65cfca496c6a701176d6e04389bb869fa (
plain)
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
|
Unicode support in busybox
There are several scenarios where we need to handle unicode
correctly.
Shell input
We want to correctly handle input of unicode characters.
There are several problems with it. Just handling input
as sequence of bytes would break any editing. This was fixed
and now lineedit operates on the array of wchar_t's.
But we also need to handle the following problematic moments:
* It is unreasonable to expect that output device supports
_any_ unicode chars. Perhaps we need to avoid printing
those chars which are not supported by output device.
Examples: chars which are not present in the font,
chars which are not assigned in unicode,
combining chars (especially trying to combine bad pairs:
a_chinese_symbol + "combining grave accent" = ??!)
* We need to account for the fact that unicode chars have
different widths: 0 for combining chars, 1 for usual,
2 for ideograms (are there 3+ wide chars?).
* Bidirectional handling. If user wants to echo a phrase
in Hebrew, he types: echo "srettel werbeH"
Editors
This case is a bit similar to "shell input", but unlike shell,
editors may encounder many more unexpected unicode sequences
(try to load a random binry file...), and they need to preserve
them, unlike shell which can afford to drop bogus input.
more, less
.
ls (multi-column display)
.
top, ps
.
Filename display (in error messages and elsewhere)
.
TODO: write an email to Asmus Freytag (asmus@unicode.org),
author of http://unicode.org/reports/tr11/
|
