diff options
| author | B. Watson <urchlay@slackware.uk> | 2024-12-12 16:46:35 -0500 |
|---|---|---|
| committer | B. Watson <urchlay@slackware.uk> | 2024-12-12 16:48:20 -0500 |
| commit | 343fd43b95960f59a3bf901f59503757b81a5592 (patch) | |
| tree | 6654e44cb883739cffbab0a7753b106f8d5c5360 /uxd.1 | |
| parent | e5735eacb8a55c147c7829c3bc9f2dfea895b165 (diff) | |
| download | uxd-343fd43b95960f59a3bf901f59503757b81a5592.tar.gz | |
fix Makefile, dashes in hex dump, red for codepoints > U+10FFFF, fix spacing.
Diffstat (limited to 'uxd.1')
| -rw-r--r-- | uxd.1 | 7 |
1 files changed, 2 insertions, 5 deletions
@@ -121,6 +121,8 @@ bytes (with their high 2 bits set to \fB10\fP). Continuation bytes that aren\(aqt preceded by a valid prefix byte. .IP \(bu 2 Truncated UTF\-8 sequence at EOF. +.IP \(bu 2 +Codepoints above U+10FFFF, which are disallowed by RFC 3629. .UNINDENT .UNINDENT .UNINDENT @@ -172,11 +174,6 @@ that could be a 1\-byte sequence, but is encoded as 2 or more). Sequences like this really should be colorized in red. Technically, this means \fBuxd\fP supports WTF\-8, not UTF\-8. .sp -RFC 3629 doesn\(aqt allow UTF\-8 to use codepoints above U+10FFFF. 4\-byte -sequences can support codepoints U+110000 to U+1FFFFF, which are not -valid Unicode. If these occur in the input, \fBuxd\fP should colorize -them in red, but it doesn\(aqt (yet). -.sp There should be options and/or a config file to change the colors, rather than baking them into the binary. .sp |