tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Steffen Nurpmeso <sdaoden@yandex.com>
Cc: tech@mdocml.bsd.lv
Subject: Re: mdocml's .Ql doesn't map to original and GNU mdoc(7)
Date: Mon, 29 Dec 2014 20:36:31 +0100	[thread overview]
Message-ID: <20141229193631.GE17408@iris.usta.de> (raw)
In-Reply-To: <20141229121746.vAh4wKsy%sdaoden@yandex.com>

Hi Steffen,

Steffen Nurpmeso wrote on Mon, Dec 29, 2014 at 01:17:46PM +0100:

> mdocml's mdoc.7 says
> 
>   Ql  single-quoted literal text: `text'
> 
> but that is not what .Ql is about:
> 
>   .Ql   The quoted literal macro behaves differently in troff
>         and nroff mode.  If formatted with @L_NROFF@(1)[221], a
>         quoted literal is always quoted.  If formatted with
>         troff, an item is only quoted if the width of the item
>         is less than three constant width characters.  This is
>         to make short strings more visible where the font
>         change to literal (constant width) is less noticeable.
> 
> The behaviour is already device-dependent in "old -mdoc", before
> 1991-03-07.

The .Ql macro is physical markup, so it is rarely used in modern
mdoc(7) documents.  Actually, i wouldn't know what purpose to
recommend it for, at all.

For terminal output, precise output compatibility with groff
matters.  For other output modes, not so much.  For a rather
obscure legacy macro such as .Ql, even less.  So i'd rather
keep output consistent across devices instead of emulating
historical behaviour.  Besides, PostScript and PDF output have
much worse formatting issues than this.  Even for HTML output,
there are more interesting things to do.

> (Without history i'm guessing, but maybe mdocml was
> ment for TTY only at first glance,

Not quite, the original motivation for mdoc*ML* was HTML output,
and for the first three months of development, HTML was the
only output mode.  Kristaps only started coding terminal output
on February 20, 2009.

> in which case the above is absolutely correct, but it lost that
> property once more output formats where added?)

No, that's not what happened.

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

  reply	other threads:[~2014-12-29 19:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29 12:17 Steffen Nurpmeso
2014-12-29 19:36 ` Ingo Schwarze [this message]
2014-12-29 20:20   ` Steffen Nurpmeso
2014-12-31 20:51     ` Ingo Schwarze
2015-01-01 19:01       ` Steffen Nurpmeso
2015-01-02 12:36         ` Ingo Schwarze
2015-01-02 14:29           ` Steffen Nurpmeso
2015-01-02 16:03             ` Ingo Schwarze
2015-01-02 18:56               ` Steffen Nurpmeso

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=20141229193631.GE17408@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=sdaoden@yandex.com \
    --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).