From: Kristaps Dzonsons <kristaps@bsd.lv>
To: Jason McIntyre <jmc@kerhand.co.uk>
Cc: "tech@mdocml.bsd.lv" <tech@mdocml.bsd.lv>
Subject: Re: [PATCH] Bd -literal/-unfilled and old groff.
Date: Tue, 27 Jul 2010 10:39:52 +0200 [thread overview]
Message-ID: <4C4E9B58.5060304@bsd.lv> (raw)
In-Reply-To: <20100727065352.GA7946@bramka.kerhand.co.uk>
>> In looking for `Sm' violators, I found that `Bd -unfilled' or `Bd
>> -literal' are playing ugly with mandoc and sub-macros.
>>
>> The following at least brings us in line with old groff (less some
>> spacing issues here and there). New groff is completely different. Sigh.
>>
>> Ingo, this is mostly for you. Thoughts? This at least fixes the main
>> violators, like awk.1, but there could be unexpected fallout. I haven't
>> been able to find any, but I didn't look too hard.
>>
>> Kristaps
>
> so, there has always been an issue that if you stick macros which change
> appearance (bold or whatever) in a literal display, you get screwy
> output. i wasn;t aware that it affects -filled/-unfilled types, but
> there you go.
>
> the awk.1 stuff is probably just wrong. our old groff formatted this
> nicely, but newer ones (understandably) dislike it. i think after
> release i will probably convert this to a list, and remove the issue.
>
> on a nice side note, your diff fixes our boot_config(8) page, which also
> has some .No within a literal display. it now formats as it should, and
> the same as new groff.
So it does! I've just committed a cleaned-up version of the patch.
Thanks,
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2010-07-27 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 23:53 Kristaps Dzonsons
[not found] ` <20100727065352.GA7946@bramka.kerhand.co.uk>
2010-07-27 8:39 ` Kristaps Dzonsons [this message]
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=4C4E9B58.5060304@bsd.lv \
--to=kristaps@bsd.lv \
--cc=jmc@kerhand.co.uk \
--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).