From: kristaps@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: Note discarding of \m, \M, and \s in COMPATIBILITY sections.
Date: Mon, 19 Jul 2010 06:48:36 -0400 (EDT) [thread overview]
Message-ID: <201007191048.o6JAmain000802@krisdoz.my.domain> (raw)
Log Message:
-----------
Note discarding of \m, \M, and \s in COMPATIBILITY sections.
Modified Files:
--------------
mdocml:
man.7
mdoc.7
Revision Data
-------------
Index: man.7
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/man.7,v
retrieving revision 1.76
retrieving revision 1.77
diff -Lman.7 -Lman.7 -u -p -r1.76 -r1.77
--- man.7
+++ man.7
@@ -910,6 +910,9 @@ language.
.Pp
.Bl -dash -compact
.It
+The \es (font size), \em (font colour), and \eM (font filling colour)
+font decoration escapes are all discarded in mandoc.
+.It
In quoted literals, GNU troff allowed pair-wise double-quotes to produce
a standalone double-quote in formatted output.
It is not known whether this behaviour is exhibited by other formatters.
Index: mdoc.7
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/mdoc.7,v
retrieving revision 1.136
retrieving revision 1.137
diff -Lmdoc.7 -Lmdoc.7 -u -p -r1.136 -r1.137
--- mdoc.7
+++ mdoc.7
@@ -2429,6 +2429,9 @@ Heirloom troff, the other significant tr
.Pp
.Bl -dash -compact
.It
+The \es (font size), \em (font colour), and \eM (font filling colour)
+font decoration escapes are all discarded in mandoc.
+.It
Old groff fails to assert a newline before
.Sx \&Bd Fl ragged compact .
.It
@@ -2476,7 +2479,7 @@ pseudo-macro as a line macro.
mandoc does.
.It
The comment syntax
-.Sq \e."
+.Sq \e\."
is no longer accepted.
.It
In groff, the
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2010-07-19 10:48 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=201007191048.o6JAmain000802@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).