From: Steffen Nurpmeso <sdaoden@yandex.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: tech@mdocml.bsd.lv
Subject: Re: mdocml's .Ql doesn't map to original and GNU mdoc(7)
Date: Fri, 02 Jan 2015 19:56:54 +0100 [thread overview]
Message-ID: <20150102185654.ZWhuJPxT%sdaoden@yandex.com> (raw)
In-Reply-To: <20150102160333.GI32031@iris.usta.de>
Hallo Ingo,
Ingo Schwarze <schwarze@usta.de> wrote:
|Steffen Nurpmeso wrote on Fri, Jan 02, 2015 at 03:29:22PM +0100:
|> No, no that is not how i see it. I _think_ of it in terms of
|> <code></code> rather than <tt></tt>. Because i only know .Dl
|> (which rather requires a leading .Pp) and ".Bd -literal" to
|> achieve the same for a block, no macro that i know of except .Ql
|> can be used to display some code inline.
|
|Oh. Now i understand why you consider it semantic markup.
|You don't consider "literal" as a font specification, but
|in the sense of "literal display", "text copied verbatim".
|
|I have no idea whether Cynthia originally considered it as
|semantic markup or as physical markup, and how much she even
|thought about the distinction (one day, i might ask her :).
|But i'm always happy if we can tweak the documentation to make stuff
|usable for semantic purposes, as long as that doesn't totally break
|existing usage - which doesn't seem the case here.
|
|So, what do you think about the following patch, documenting
|it as semantic rather than physical markup? I think i now like
|the idea, one more semantic macro, one less physical. :-)
I like that!
--steffen
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2015-01-02 18:56 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
2015-01-02 14:29 ` Steffen Nurpmeso
2015-01-02 16:03 ` Ingo Schwarze
2015-01-02 18:56 ` Steffen Nurpmeso [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=20150102185654.ZWhuJPxT%sdaoden@yandex.com \
--to=sdaoden@yandex.com \
--cc=schwarze@usta.de \
--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).