From: Steffen Nurpmeso <sdaoden@yandex.com>
To: discuss@mdocml.bsd.lv
Subject: Re: Redux: linking in mdoc(7)?
Date: Tue, 05 May 2015 15:47:14 +0200 [thread overview]
Message-ID: <20150505134714.yhPAIfZcwj8BIIoZwMCiZQ==@yandex.com> (raw)
In-Reply-To: <20150501200434.DOdMf7wQvHU=%sdaoden@yandex.com>
FYI,
i've completed the mdocmx(7) side of the road.
Ciao.
Freely definable anchors and references[15]
Via the ‘.Mx -ix category key’ and ‘.Mx -ix key’ usage forms anchors can
(Btw., does anone knows how to do that as
.Mx -ix [category] key
i.e., using .Op for category --- while still having the entire
thing inside of, and quoted by, .Ql? mdoc(7) no-go i guess?)
be defined almost anywhere, e.g., ‘.Mx -ix subsubsection "An interesting
topic"’ defines the anchor ‘An interesting topic’ for the “key”
‘subsubsection’. The form without a specified category will use the
builtin name ‘ixsx’ instead.
References to anchors that have been created via -ix can be made by acti‐
vating the .Sx search extension via ‘.Mx -sx category’ (or ‘.Mx -sx’ for
the builtin ‘ixsx[58]’ category) followed by a normal local reference
lookup:
.Mx -sx subsubsection
.Sx "An interesting topic"
It should be noted that these usage forms are mostly ment for automated
conversion tools rather than for human manual creators: their use is non-
trivial (which is owed to the implementation of mdoc(7)[59]) and the
resulting visual output should always be verified! As a rule of thumb
anchors should always be created inside some “normal” text so that they
can be attached to something “physical”.
--steffen
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2015-05-05 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 15:42 Kristaps Dzonsons
2015-04-30 17:31 ` Steffen Nurpmeso
2015-04-30 23:06 ` Kristaps Dzonsons
2015-05-01 20:04 ` Steffen Nurpmeso
2015-05-05 13:47 ` 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='20150505134714.yhPAIfZcwj8BIIoZwMCiZQ==@yandex.com' \
--to=sdaoden@yandex.com \
--cc=discuss@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).