aboutsummaryrefslogtreecommitdiff
path: root/debug.h
diff options
context:
space:
mode:
authorCraig Barnes <craigbarnes@protonmail.com>2021-05-25 18:14:06 +0000
committerCraig Barnes <craigbarnes@protonmail.com>2021-05-25 20:37:38 +0000
commit14a55de4e721283ab4e9a04ed58db6cecd5fcaa1 (patch)
treee3a52a7e6737ee7eeb5432fc74e54d4e634ae22d /debug.h
parentpkgbuild: bump fcft requirement to 2.4.0 (diff)
vt: remove partial support for 8-bit C1 control chars
These are part of the "anywhere" state in Paul Flo Williams' VT parser state diagram[1]. That means that they should be accepted *anywhere* in a byte sequence, including in the middle of other sequences or even in the middle of a multi-byte UTF-8 sequence. Adhering to this requirement makes them incompatible with the use of UTF-8 as a universal encoding. Not adhering to the aforementioned requirement by making a special case for UTF-8 sequences may seem tempting, but it's much more at odds with the relevant standards[2] than it appears on the surface. UTF-8 is not an "8-bit code", at least not according to the parlance of ECMA-43, nor does it map the C1 control range in a compatible way. [1]: https://vt100.net/emu/dec_ansi_parser [2]: ECMA-35, ECMA-43, ECMA-48
Diffstat (limited to 'debug.h')
0 files changed, 0 insertions, 0 deletions