summaryrefslogtreecommitdiff
path: root/Config.in
diff options
context:
space:
mode:
authorDenys Vlasenko2010-01-31 18:12:57 +0100
committerDenys Vlasenko2010-01-31 18:12:57 +0100
commit460f8276449f0933f242c9295b241ec213bcef82 (patch)
tree1ab106c367abef17504d1e30aac7408745144043 /Config.in
parentb1edf20f1848cd741e8a8395afb4a4655a210906 (diff)
downloadbusybox-460f8276449f0933f242c9295b241ec213bcef82.zip
busybox-460f8276449f0933f242c9295b241ec213bcef82.tar.gz
better wording in Config
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'Config.in')
-rw-r--r--Config.in12
1 files changed, 9 insertions, 3 deletions
diff --git a/Config.in b/Config.in
index b4ea702..e7bb05d 100644
--- a/Config.in
+++ b/Config.in
@@ -161,9 +161,11 @@ config LAST_SUPPORTED_WCHAR
The idea is that many valid printable Unicode chars are
nevertheless are not displayed correctly. Think about
- combining charachers, double-wide hieroglyphs and such.
- Many terminals, xterms and such will fail to handle them
- correctly.
+ combining charachers, double-wide hieroglyphs, obscure
+ characters in dozens of ancient scripts...
+ Many terminals, terminal emulators, xterms etc will fail
+ to handle them correctly. Choose the smallest value
+ which suits your needs.
Typical values are:
126 - ASCII only
@@ -172,6 +174,10 @@ config LAST_SUPPORTED_WCHAR
code is ~700 bytes smaller for this case.
4351 (0x10ff) - there are no double-wide chars in [0..4351] range,
code is ~300 bytes smaller for this case.
+ 12799 (0x31ff) - nearly all non-ideographic characters are
+ available in [0..12799] range, including
+ East Asian scripts like katakana, hiragana, hangul,
+ bopomofo...
0 - off, any valid printable Unicode character will be printed.
config UNICODE_COMBINING_WCHARS