discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Thomas Klausner <wiz@netbsd.org>
Cc: discuss@mdocml.bsd.lv
Subject: Re: mandoc and nroff differs for Em macro construct in columnated list
Date: Wed, 12 Oct 2011 02:18:12 +0200	[thread overview]
Message-ID: <20111012001812.GA10686@iris.usta.de> (raw)
In-Reply-To: <20111011222000.GK25396@danbala.tuwien.ac.at>

Hi Thomas,

Thomas Klausner wrote on Wed, Oct 12, 2011 at 12:20:00AM +0200:

> In a columnated list, use of Em macro differs with a quoted string of
> words separated by tab characters. While nroff do emphasis all words,
> mandoc do only make the first one.

Yes, this is a known bug in mandoc.
It is listed in the TODO list here:

- In .Bl -column,
  .It Em Authentication<tab>Key Length
  ought to render "Key Length" with emphasis, too,
  see OpenBSD iked.conf(5).

Actually, it's one of the nastier bugs we have and not at all
easy to fix.  It's a bad nesting issue:

  begin .It
    begin .Ta
      begin .Em
    end .Ta
    begin .Ta
    end .Ta
      end .Em
  end .It

Two blocks (.Ta and .Em) overlap, but none of them fully contains
the other.  On top of that, .Ta requires different handling
depending on whether it's written "Ta" or <tab>.  And on top
of that, the quoted string also spans blocks.

I have implemented bad nesting support for .Xo some time ago,
but this case it yet more complicated since .Bl -column is by
far the most complicated mdoc block even without such additional
complications.

I hope we will come round to fix that one day, but it's not
going to be quick or easy.

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

      reply	other threads:[~2011-10-12  0:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11 22:20 Thomas Klausner
2011-10-12  0:18 ` Ingo Schwarze [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=20111012001812.GA10686@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mdocml.bsd.lv \
    --cc=wiz@netbsd.org \
    /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).