From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Cc: jmc@openbsd.org
Subject: Re: mdocml: Import changes by schwarze@ and Jason McIntyre into manuals.
Date: Sun, 19 Dec 2010 09:23:02 +0100 [thread overview]
Message-ID: <20101219082302.GB17028@iris.usta.de> (raw)
In-Reply-To: <201012061637.oB6GbW9j031066@krisdoz.my.domain>
Hi Kristaps,
kristaps@mdocml.bsd.lv wrote on Mon, Dec 06, 2010 at 11:37:32AM -0500:
> Log Message:
> -----------
> Import changes by schwarze@ and Jason McIntyre into manuals. These are
> for the new libroff macros, the new libman macros, and for the sake of
> general clarity.
>
> Note that `ft' documentation is NOT included, as I've kept it in -man:
> it's highly confusing to have it in roff.7 when it's not implemented for
> both -man and -mdoc, as at least in theory, roff.7 should include only
> macros recognised by BOTH formats.
>
> Modified Files:
> --------------
> mdocml:
> mdoc.7
> roff.7
Our manuals are now back in sync.
Note that i left .ft in roff(7) for now because i failed to make up
my mind about it. Your reasoning of course makes a lot of sense.
On the other hand:
It's a bug that mdoc(7) does not recognize .ft, even if using
.ft in mdoc(7) should clearly be discouraged - but .ft is a roff(7)
request, not a man(7) macro.
Adding .ft to mdoc(7) has no priority, it is hardly used there.
Besides being unwilling to waste my time adding .ft to mdoc(7),
i'm even a bit reluctant to encumber mdoc(7) with it:
I'm still dreaming about a common request/macro table that will
always include roff(7) macros, including .br, .sp, .ft, .de, .ds
and so on, being extended by macros when man(7) or mdoc(7) get
loaded, and being overwritten by .de and .ds. It is not urgent
at all, but i hope that at some point we can do it. There is
no finished design yet, it's just a nebulous idea.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
parent reply other threads:[~2010-12-19 8:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <201012061637.oB6GbW9j031066@krisdoz.my.domain>]
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=20101219082302.GB17028@iris.usta.de \
--to=schwarze@usta.de \
--cc=jmc@openbsd.org \
--cc=tech@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).