From fd3a982e26813f5bcc82c7e89ce6fa2ad44432bf Mon Sep 17 00:00:00 2001 From: tpearson Date: Fri, 7 Jan 2011 04:10:07 +0000 Subject: Revert automated changes Sorry guys, they are just not ready for prime time Work will continue as always git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdebase@1212480 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- konsole/README.unicode | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) (limited to 'konsole/README.unicode') diff --git a/konsole/README.unicode b/konsole/README.unicode index b366a6bad..bf8134674 100644 --- a/konsole/README.unicode +++ b/konsole/README.unicode @@ -1,6 +1,6 @@ -[README.tqunicode] +[README.unicode] -Konsole supports tqunicode, which means one can display up +Konsole supports unicode, which means one can display up to 64K different glyphs at the same time on one screen. The enhancement is pretty complete and the main current @@ -9,7 +9,7 @@ within localed environments. At least the european locales should be enabled to use their local scripts when running konsole. -To fully install it, please get a complete set of tqunicode +To fully install it, please get a complete set of unicode enhanced fixed fonts from . @@ -29,36 +29,36 @@ Also, a new linux console font has been converted for X11. This font has iso10646-1 encoding and the usual vga glyphs. -* A more precise anatomy of tqunicode support within konsole +* A more precise anatomy of unicode support within konsole -The internal character representation is uniquely 16 bit tqunicode. +The internal character representation is uniquely 16 bit unicode. All in- and output connections of konsole (beside the mouse) are filtered through three different codecs (corresponding to 2 different codes): - 1) Font Code - The renderer converts from tqunicode to the code of + 1) Font Code - The renderer converts from unicode to the code of the font to the degree that code is supported within Qt. - Non-iso10646 (tqunicode) codes are considered to be VT100 - enhanced, meaning that 0x00 .. 0x1f tqcontains the VT100 + Non-iso10646 (unicode) codes are considered to be VT100 + enhanced, meaning that 0x00 .. 0x1f contains the VT100 graphical characters. 2) Client Code - This is used for bytes from and to the pty. Often, the clients code is identical with the locale setting. -Thus, tqunicode support mainly turns out to be a potter's wheel of +Thus, unicode support mainly turns out to be a potter's wheel of code conversions. Beside these conversions, up to 2^16 diffent glyphs can be displayed now. Though it is not possible to type each of these codes, one can use utf-8 encoding on the clients side. -Please note that tqunicode support is still under development in +Please note that unicode support is still under development in the freeware community and is not supported by terminal aware applications, since ncurses does currently not provide wide character operations. -Because utf-8 tqcontains ascii-7 properly, one can work with utf-8 +Because utf-8 contains ascii-7 properly, one can work with utf-8 enabled as long as no international characters are used. Try to cat 9x15.repertoire-utf8 from the test when having utf-8 encoding enabled. @@ -66,7 +66,7 @@ enabled. Utf-8 code is enabled and disabled by sending %G or %@. The utf8.sh utility in the test directory does this. -Though utf8 properly tqcontains ascii-7 note that the length of a +Though utf8 properly contains ascii-7 note that the length of a utf8 encoded string differs from the length of the string itself. This confuses many length aware programs as soon as proper (non- ascii-7 characters) are used, this may result in deviating cursor -- cgit v1.2.3