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: Fri, 2 Jan 2015 13:36:36 +0100 [thread overview]
Message-ID: <20150102123636.GF32031@iris.usta.de> (raw)
In-Reply-To: <20150101190136.03oKSkqW%sdaoden@yandex.com>
Hi Steffen,
Steffen Nurpmeso wrote on Thu, Jan 01, 2015 at 08:01:36PM +0100:
> seems to happily ignore to replace that style-centric
>
> -.It Sx \&Ql Ta single-quoted literal text: Ql text
>
> with the definitely more correct semantics-centric
>
> +.It Sx \&Ql Ta format quoted literal text: Ql text
>
> which the quoted literal mark-up command .Ql is all about.
The mdoc(7) language is somewhat inconsistent in the following
respect: It contains many macros that are purely semantic, but also
some that are purely presentational (and even some abominations
that are a bit of both, like .Tn). It's the same ailing that
traditional HTML had, and that is now mostly resolved in HTML5 -
no wonder since both mdoc(7) and traditional HTML date from the
same time, plus/minus less than five years.
The .Ql macro is one of those that are purely presentational.
It requests two things: "literal font" (which is a purely
presentational aspect) and "single quotes" (which is a purely
presentational aspect just as well).
So, for a one-line description, "single-quoted literal" is as
exact as it gets: both making it clear that this is purely
presentational, and stating precisely how it looks.
Your proposed wording "format quoted literal" does *not* indicate
any semantic expressiveness either, so i don't understand why you
call it "semantics-centric". Besides, it has two issues:
1. The word "format" is redundant. It is implied by the purpose
of the MACRO OVERVIEW list and applies to all macros.
Consequently, not a single instance of that word exists
in the whole section.
2. Dropping the word "single" seems wrong. It merely loses
precision for no good reason that i can see. That's
particularly bad since all the other entries for "Physical
enclosures" explicitly name the enclosing character.
So i don't understand why you call it "more correct".
> But now i feel rather hesitant.. and.. no, i won't continue.
Well, *if* i am wrong, i'm willing to learn in which way.
Happy New Year for you,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2015-01-02 12: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
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 [this message]
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=20150102123636.GF32031@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).