[konsole] [Bug 395171] Remove UTF-16 and other non ASCII compatible encodings

[Egmont Koblinger]

https://bugs.kde.org/show_bug.cgi?id=395171

--- Comment #15 from Egmont Koblinger <egmont at gmail.com> ---
I did indeed make a technical mistake.

For some mysterious reason, what I incorrectly had in my mind was that the
boundary beyond BMP (i.e. at U+FFFF) is where UTF-8 increases from 2 bytes to
3. This is indeed not correct, this is where it increases from 3 bytes to 4.
The increase from 2 bytes to 3 happens at a much lower codepoint. Therefore,
indeed, there are many letter-based scripts that use 3 bytes per letter in
UTF-8.

I wrote the CJK stuff with this mistake in mind. I was technically incorrect,
and for this I do apologize from everyone.

* * *

That being said:

- Jayadevan still does not understand, and apparently still refuses to even try
to understand, that UTF-16 cannot be made to work in terminals for a plethora
of reasons, including, but not limited to the fact that all components of the
system that interact with terminals only support ASCII-compatible encodings
there;

- ignores that UTF-16 mode never worked; that is, firmly speaks up against
removing something that, again, *never* *worked*, *still* *does* *not* *work*
and *can* *not* *be* *fixed*;

- ignores that the work happening inside terminal emulators is typically
English-centric by its nature;

- ignores that the difference in the byte count simply does not matter at all;

- ignores that choosing one technical solution over the other, even if that
technical solution results in a higher network traffic for some languages vs. a
lower one for some others, is no discrimination whatsoever (and even if it was,
the right place to complain would be the Unicode Consortium, and not Konsole);

- ignores that even if terminals and their surrounding infrastructure could
implement UTF-16 support (which, again, they cannot reasonably do), this would
mean switching from 1 standard to 2 incompatible ones being used concurrently,
which would obviously bring plenty of problems (the very exact problem that
Unicode was meant to fix) and would not solve anything;

- in comments 7 & 9 used wording that are at the very least borderline
unacceptable.

-- 
You are receiving this mail because:
You are the assignee for the bug.