From: kristaps@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: Remove the pod2man table entries.
Date: Sun, 29 Aug 2010 07:36:49 -0400 (EDT) [thread overview]
Message-ID: <201008291136.o7TBanHC003442@krisdoz.my.domain> (raw)
Log Message:
-----------
Remove the pod2man table entries. They can now be properly read and
assigned within the pod2man preamble.
Modified Files:
--------------
mdocml:
chars.c
chars.in
Revision Data
-------------
Index: chars.c
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/chars.c,v
retrieving revision 1.27
retrieving revision 1.28
diff -Lchars.c -Lchars.c -u -p -r1.27 -r1.28
--- chars.c
+++ chars.c
@@ -40,7 +40,7 @@ struct ln {
#define CHARS_BOTH (CHARS_CHAR | CHARS_STRING)
};
-#define LINES_MAX 369
+#define LINES_MAX 362
#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.33
retrieving revision 1.34
diff -Lchars.in -Lchars.in -u -p -r1.33 -r1.34
--- chars.in
+++ chars.in
@@ -322,8 +322,8 @@ CHAR("fi", "fi", 64257)
CHAR("fl", "fl", 64258)
CHAR("Fi", "ffi", 64259)
CHAR("Fl", "ffl", 64260)
-BOTH("AE", "AE", 198)
-BOTH("ae", "ae", 230)
+CHAR("AE", "AE", 198)
+CHAR("ae", "ae", 230)
CHAR("OE", "OE", 338)
CHAR("oe", "oe", 339)
CHAR("ss", "ss", 223)
@@ -360,13 +360,6 @@ STRING("^", "^", 94)
STRING(",", ",", 44)
STRING("~", "~", 126)
STRING("/", "/", 47)
-STRING(":", "\"", 776)
-STRING("8", "B", 946)
-STRING("o", "o", 176)
-STRING("D-", "D", 208)
-STRING("d-", "o", 240)
-STRING("Th", "b", 222)
-STRING("th", "b", 254)
/* Old style. */
STRING("Am", "&", 38)
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2010-08-29 11:36 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=201008291136.o7TBanHC003442@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).