aboutsummaryrefslogtreecommitdiff
path: root/uxd.1
diff options
context:
space:
mode:
authorB. Watson <urchlay@slackware.uk>2024-12-17 22:47:36 -0500
committerB. Watson <urchlay@slackware.uk>2024-12-17 22:47:57 -0500
commitf0e0a74cbf43d771075ad2d801197b8072d5b15c (patch)
tree71d2f41619aa4cc39487c850a59e97f90895669b /uxd.1
parent548e7d04b4b2fa60b71615ed590be54016dac52d (diff)
downloaduxd-f0e0a74cbf43d771075ad2d801197b8072d5b15c.tar.gz
uxd.c: add overlong sequence detection; ver.rst: regenerate
Diffstat (limited to 'uxd.1')
-rw-r--r--uxd.125
1 files changed, 13 insertions, 12 deletions
diff --git a/uxd.1 b/uxd.1
index 35bfc4f..ca39178 100644
--- a/uxd.1
+++ b/uxd.1
@@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
..
-.TH "UXD" 1 "2024-12-17" "0.1.0" "Urchlay's Utilities"
+.TH "UXD" 1 "2024-12-17" "0.2.1" "Urchlay's Utilities"
.SH NAME
uxd \- UTF-8 hex dumper
.SH SYNOPSIS
@@ -270,15 +270,21 @@ changed with the \fB\-c\fP option (see above).
Printable characters (except the space, U+0020) alternate between green and yellow.
.TP
.B \fBpurple\fP
-Spaces and unprintable characters ("control" characters, newlines, tabs, etc).
-These are printed as "visible" characters, e.g. ␣ for the space, ↵ for a newline.
-Hopefully this is an improvement over the usual practice of printing these as periods, like
-standard hex dumpers do. The Unicode BOM (byte order marker, U+FEFF) is printed
+Spaces and unprintable characters ("control" characters, newlines,
+tabs, etc). These are printed as "visible" characters, e.g. ␣ for
+the space, ↵ for a newline. Hopefully this is an improvement over
+the usual practice of printing these as periods, like standard hex
+dumpers do. The Unicode BOM (byte order marker, U+FEFF) is printed
as a purple letter B.
+.sp
+Note: Overlong encodings (e.g. codepoints U+0000 to U+007F encoded
+as 2 or more bytes) are rendered as � (U+0FFD) in reverse video
+purple.
.TP
.B \fBred\fP
-Invalid UTF\-8 sequences. These are rendered with a red background, to make them
-stand out. Examples of invalid sequences:
+Invalid UTF\-8 sequences. These are rendered as � (U+0FFD) with
+a red background, to make them stand out. Examples of invalid
+sequences:
.INDENT 7.0
.INDENT 3.5
.INDENT 0.0
@@ -359,11 +365,6 @@ input file. Invalid input (non\-UTF\-8) doesn\(aqt count as an error;
it\(aqll just have lots of red in the output.
.SH BUGS
.sp
-\fBuxd\fP doesn\(aqt check for overlong UTF\-8 encodings (e.g. a character
-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
There should be options and/or a config file to change the colors,
rather than baking them into the binary.
.sp