Rudimentary implementation of the roff(7) .char (output glyph

definition) request, used for example by groff_hdtbl(7).

This simplistic implementation may interact incorrectly
with the .tr (input character translation) request.
But come on, you are not only using .char *and* .tr, but you do so
with respect to the same character in the same manual page?

1 files changed, 2 insertions, 0 deletions

diff --git a/read.c b/read.c
index 84e70afc..8bf0ef84 100644
--- a/read.c
+++ b/read.c
@@ -198,6 +198,7 @@ static	const char * const	mandocerrs[MANDOCERR_MAX] = {
 	"unknown library name",
 	"invalid content in Rs block",
 	"invalid Boolean argument",
+	"argument contains two font escapes",
 	"unknown font, skipping request",
 	"odd number of characters in request",
 
@@ -252,6 +253,7 @@ static	const char * const	mandocerrs[MANDOCERR_MAX] = {
 	"skipping display without arguments",
 	"missing list type, using -item",
 	"argument is not numeric, using 1",
+	"argument is not a character",
 	"missing manual name, using \"\"",
 	"uname(3) system call failed, using UNKNOWN",
 	"unknown standard specifier",