From 460f8276449f0933f242c9295b241ec213bcef82 Mon Sep 17 00:00:00 2001 From: Denys Vlasenko Date: Sun, 31 Jan 2010 18:12:57 +0100 Subject: better wording in Config Signed-off-by: Denys Vlasenko --- Config.in | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) (limited to 'Config.in') diff --git a/Config.in b/Config.in index b4ea70242..e7bb05dce 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 -- cgit v1.2.3-55-g6feb