From: kristaps@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: Remove \*(C+ from the pre-predefined strings.
Date: Mon, 16 Aug 2010 05:51:17 -0400 (EDT) [thread overview]
Message-ID: <201008160951.o7G9pHRD015038@krisdoz.my.domain> (raw)
Log Message:
-----------
Remove \*(C+ from the pre-predefined strings. It is always `ds'-defined
when being used in manuals. Since we now support `ds', it's no longer
necessary to account for it. From a bug report originally by Thomas
Jeunet.
Modified Files:
--------------
mdocml:
TODO
chars.c
chars.in
man.3
Revision Data
-------------
Index: chars.c
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/chars.c,v
retrieving revision 1.25
retrieving revision 1.26
diff -Lchars.c -Lchars.c -u -p -r1.25 -r1.26
--- chars.c
+++ chars.c
@@ -40,7 +40,7 @@ struct ln {
#define CHARS_BOTH (CHARS_CHAR | CHARS_STRING)
};
-#define LINES_MAX 370
+#define LINES_MAX 369
#define CHAR(in, ch, code) \
{ NULL, (in), (ch), (code), CHARS_CHAR },
Index: chars.in
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/chars.in,v
retrieving revision 1.32
retrieving revision 1.33
diff -Lchars.in -Lchars.in -u -p -r1.32 -r1.33
--- chars.in
+++ chars.in
@@ -353,7 +353,6 @@ STRING("--", "--", 8212)
STRING("PI", "pi", 960)
STRING("L\"", "``", 8220)
STRING("R\"", "\'\'", 8221)
-STRING("C+", "C++", 0)
STRING("C`", "`", 8216)
STRING("C\'", "\'", 8217)
STRING("Aq", "\'", 39)
Index: TODO
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/TODO,v
retrieving revision 1.39
retrieving revision 1.40
diff -LTODO -LTODO -u -p -r1.39 -r1.40
--- TODO
+++ TODO
@@ -179,3 +179,7 @@ Several areas can be cleaned up to make
in OpenBSD ksh(1) gives the wrong width
because "\e" is one character in groff, two in mandoc
+- Now that `ds' is minimally supported, we can get rid of some
+ predefined strings. \*(C+ has already been thrown out. Track these
+ down and whack them. Look in e.g. gcc.1 for the top-level `ds'
+ invocations. These are reproduced across most crappy GNU manuals.
Index: man.3
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/man.3,v
retrieving revision 1.22
retrieving revision 1.23
diff -Lman.3 -Lman.3 -u -p -r1.22 -r1.23
--- man.3
+++ man.3
@@ -116,7 +116,6 @@ documents to be correctly formatted:
\e*(PI (pi),
\e*(L" (left double-quote),
\e*(R" (right double-quote),
-\e*(C+ (C++),
\e*(C` (left single-quote),
\e*(C' (right single-quote),
\e*(Aq (apostrophe),
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2010-08-16 9:51 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201008160951.o7G9pHRD015038@krisdoz.my.domain \
--to=kristaps@mdocml.bsd.lv \
--cc=source@mdocml.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).