discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Thomas Klausner <wiz@NetBSD.org>
To: Ingo Schwarze <schwarze@usta.de>
Cc: discuss@mdocml.bsd.lv
Subject: Re: Space after .E[dl...]?
Date: Wed, 23 Nov 2011 13:54:26 +0100	[thread overview]
Message-ID: <20111123125426.GT9000@danbala.tuwien.ac.at> (raw)
In-Reply-To: <20111123003118.GA24880@iris.usta.de>

On Wed, Nov 23, 2011 at 01:31:19AM +0100, Ingo Schwarze wrote:
> However, this is not just a question of what we like better,
> but also a question of compatibility.  There are three aspects
> to compatibility:

I understand your point. Most (if not all) mdoc man pages that a
typical BSD user is interested in will come with their operating
system though, so I don't see it as such a big hindrance as you do,
because we can fix them.

> (3) There are thousands of real-world manuals written for the
> old behaviour.  Quite probably, there are some that will look
> worse after the change because the additional blank line is not
> an improvement in their particular case, even if it is in many
> other cases, and the authors of course relied on the fact that
> there is no blank line.  Before even proposing this change in
> the language definition, i'd like some rough estimate, or at
> least feeling, how many pages might be affected by this effect,
> and how much effort we are imposing on people like jmc@ to
> clean up the tree after the change.

For backwards compat, I'd like to have Pp after El etc. ignored; this
should fix this problem.

Thanks for your feedback!
 Thomas
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2011-11-23 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 22:34 Thomas Klausner
2011-11-23  0:31 ` Ingo Schwarze
2011-11-23 12:54   ` Thomas Klausner [this message]
2011-11-23 23:54     ` Ingo Schwarze

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=20111123125426.GT9000@danbala.tuwien.ac.at \
    --to=wiz@netbsd.org \
    --cc=discuss@mdocml.bsd.lv \
    --cc=schwarze@usta.de \
    /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).