From: Steffen Nurpmeso <sdaoden@yandex.com>
To: discuss@mdocml.bsd.lv
Subject: Re: Redux: linking in mdoc(7)?
Date: Fri, 01 May 2015 22:04:34 +0200 [thread overview]
Message-ID: <20150501200434.DOdMf7wQvHU=%sdaoden@yandex.com> (raw)
In-Reply-To: <5542B58F.50608@bsd.lv>
Happy 1st of May :o,
Kristaps Dzonsons <kristaps@bsd.lv> wrote:
|with the existing (and many) Texinfo and DocBook documents, both of
|which allow and use intra-document linking.
How about that?
It is missing mdocmx.sh preprocessor support yet (so that only
references to anchors already defined work).
.....
commit 7b77631 (HEAD, refs/heads/crawl)
Author: Steffen Nurpmeso <sdaoden@users.sf.net>
Date: 2015-05-01 21:51:10 +0200
FIXME [mdocmx] Add ".Mx -ix [CAT] KEY" and ".Mx -sx [CAT]" \
(Kristaps Dzonsons)..
Kristaps Dzonsons (kristaps at bsd dot lv) prodded multiple times
for freely definable anchors on (discuss at mdocml dot bsd dot lv)
in order to be able to implement texi2mdoc etc.
This is my proposed solution, and it'll do fine if the anchor is
placed carefully, which should be no problem for automated
converters.
.....
Note that in the next anchors[57] refers to the freely defined
"usage forms anchors" in the first text line (you would see it
with -dmx-debug=1).
.....
Freely definable anchors and references[15]
Via the ‘.Mx -ix category key’ and ‘.Mx -ix key’ usage forms anchors can
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[57] that have been created via -ix can be made by
activating the .Sx search extension via ‘.Mx -sx category’ (or ‘.Mx -sx’
for the builtin ‘ixsx’ 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)[58]) and the
resulting visual output should always be verified! As a rule of thumb
anchors should always 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
next prev parent reply other threads:[~2015-05-01 20:04 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 [this message]
2015-05-05 13:47 ` 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='20150501200434.DOdMf7wQvHU=%sdaoden@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).