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
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
With this option off, any Unicode char with width > 1
is substituted on output.
+config UNICODE_BIDI_SUPPORT
+ bool "Bidirectional character-aware line input"
+ default y
+ depends on FEATURE_ASSUME_UNICODE && !LOCALE_SUPPORT
+ help
+ With this option on, right-to-left Unicode characters
+ are treated differently on input (e.g. cursor movement).
+
config LONG_OPTS
bool "Support for --long-options"
default y