From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: mdoc(7) COMPATIBILITY
Date: Sat, 21 Aug 2010 22:20:16 +0200 [thread overview]
Message-ID: <4C703500.4010404@bsd.lv> (raw)
In-Reply-To: <20100821201206.GA9511@iris.usta.de>
>> That reminds me: can you put a note in mdoc.7 COMPATIBILITY?
>
> Uh.
> I felt unable to decide where to put it...
>
> So, here is a proposal to sort that section by macro names,
> to uniformly put these at the beginning of each line,
> in order to make it easier to navigate,
> and to distinguish shortcomings in groff from
> unimplemented features in mandoc.
>
> I have removed a few entries because they seem untrue or
> irrelevant:
>
> - "The comment syntax `\."' is no longer accepted."
> It is discouraged, but mandoc does accept it.
> - .Bd -ragged = -filled, -literal = -unfilled
> I'm not aware of any real difference between groff and mandoc
> in this respect.
> - .Cd was restricted to section 4 manuals.
> .Er was restricted to section 2 manuals.
> .Ex was restricted to section 1, 6, and 8 manuals.
> .Rv was restricted to section 2 and 3 manuals.
> Actually, groff always renders these macros correctly,
> even though it warns about .Ex and .Rv used elsewhere.
>
> Of course, i have also added the sentence about spacing in
> .Bd -column, now that it's clear where to put it. ;-)
Ingo,
I like this approach. What follows are some further suggestions.
First, there are a few more escapes we ignore; check mandoc.c and/or
out.c for the scoop.
Second, can you treat the man.7 manual the same way? For consistency.
I'm still on the fence as to whether \f and friends should be in
mandoc_char.7 or something to avoid duplication across man.7 and mdoc.7.
Third, let's make
- The \m (font colour), \M (font filling colour), and \s
(font size) font decoration escapes are all discarded in
mandoc.
- The `f' scaling unit is accepted by mandoc, but rendered as
the default unit.
so that it's consistently
- The \f (font) scaling unit is accepted by mandoc, but
^^^^^^^^
rendered as the default unit.
In general, the escapes are sometimes quoted with e.g. `\f' and
sometimes not. These should be unified.
I also note, very particularly, that \m and friends are font decorations
but text decorations...
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-08-21 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201008202251.o7KMpT4F020687@krisdoz.my.domain>
2010-08-21 11:18 ` mdocml: .Bl -column phrases ignore spacing rules for trailing Kristaps Dzonsons
2010-08-21 16:06 ` Ingo Schwarze
2010-08-21 17:29 ` Kristaps Dzonsons
2010-08-21 20:12 ` mdoc(7) COMPATIBILITY Ingo Schwarze
2010-08-21 20:20 ` Kristaps Dzonsons [this message]
2010-08-22 9:27 ` Kristaps Dzonsons
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=4C703500.4010404@bsd.lv \
--to=kristaps@bsd.lv \
--cc=discuss@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).