tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: "Anthony J. Bentley" <anthony@anjbe.name>
Cc: tech@mdocml.bsd.lv
Subject: Re: Groff difference: punctuation following Lk
Date: Mon, 10 Apr 2017 02:49:24 +0200	[thread overview]
Message-ID: <20170410004924.GA50206@athene.usta.de> (raw)
In-Reply-To: <65939.1491774443@cathet.us>

Hi Anthony,

Anthony J. Bentley wrote on Sun, Apr 09, 2017 at 03:47:23PM -0600:

> I like it very much.

Good, thanks for having a look, submitted to groff.

> Groff's output still differs in two ways that I can see.

Yes, i'm aware of these two differences, but followed the
concept of "one change at a time".

> The first is that it doesn't handle multiple arguments well:
> 
> .Lk https://www.example.com/ a b c
> 
> becomes "a: https://www.example.com/ b c" in groff (b and c bolded),
> instead of "a b c: https://example.com/" in mandoc.

I agree that the mandoc behaviour is useful and the groff behaviour
is useless, confusing, and likely unintentional.  I'll probably
look whether groff can be improved.  I can't believe anybody relies
on the current behaviour.

> The other is that URLs of a certain size (I think that's the criteria?)
> get indented in groff. You can see this in sendbug(1), for example:
> 
>      The status of bug reports can be followed by checking the
>      bugs@openbsd.org mailing list archive available at
>            http://marc.info/?l=openbsd-bugs.
> 
> Reducing the URL to 25 characters removes the indent:
> 
>      The status of bug reports can be followed by checking the
>      bugs@openbsd.org mailing list archive available at
>      http://marc.info/?l=openb.

Yes, doc.tmac-u hardcodes a limit for inserting a virtual .D1 macro
of >= 26\(en for nroff, but 38 for troff.  That is weird, but the
end-result usually looks OK, ...

> Mandoc doesn't indent in either case.

 ... so probably mandoc should follow.

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2017-04-10  0:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01  9:29 Anthony J. Bentley
2017-04-09 21:22 ` Ingo Schwarze
2017-04-09 21:47   ` Anthony J. Bentley
2017-04-10  0:49     ` Ingo Schwarze [this message]
2017-04-11 13:58       ` Ingo Schwarze
2017-04-12  4:17         ` Anthony J. Bentley

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=20170410004924.GA50206@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=anthony@anjbe.name \
    --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).