help / color / mirror / Atom feed
Subject: mandoc: John Gardner: handling of ASCII control characters during input
Date: Mon, 22 Jun 2020 13:01:01 -0500 (EST)	[thread overview]
Message-ID: <> (raw)

Log Message:
John Gardner: handling of ASCII control characters during input

Modified Files:

Revision Data
Index: TODO
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.302
retrieving revision 1.303
diff -LTODO -LTODO -u -p -r1.302 -r1.303
--- TODO
+++ TODO
@@ -83,6 +83,20 @@ are mere guesses, and some may be wrong.
   Jan Stary 20 Apr 2019 20:16:54 +0200
   loc *  exist ***  algo ***  size **  imp *
+- mandoc replaces all ASCII control characters except tab and line feed
+  with '?' during input.  It would be better to replace them with
+  Unicode escapes in preconv_encode() or somewhere in the vicinity,
+  such that the already existing better replacement strings show
+  up in the output.  Emulating groff is not desirable: groff replaces
+  0x00, 0x0b, and 0x0d to 0x1f with the empty string (bad because
+  that's easy to overlook for the document author), 0x01 with '.'
+  (very confusing), and passes through 0x02 to 0x08, 0x0c, and 0x7f
+  raw (bad because that is insecure output).  Remember that 0x07 may
+  need special handling because it is sometimes used for certain
+  delimiters, so it may need handling *after* roff.c rather than before.
+  reminded by John Gardner 16 Jun 2020 14:26:28 +1000
+  loc **  exist **  algo **  size **  imp *
 --- missing mdoc features ----------------------------------------------
 - .Sh and .Ss should be parsed and partially callable, see groff_mdoc(7)
 To unsubscribe send an email to

                 reply	other threads:[~2020-06-22 18:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).