From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from forward4h.cmail.yandex.net (forward4h.cmail.yandex.net [87.250.230.19]); by fantadrom.bsd.lv (OpenSMTPD) with ESMTP id 94a91921; for ; Fri, 1 May 2015 15:04:47 -0500 (EST) Received: from smtp3o.mail.yandex.net (smtp3o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::27]) by forward4h.cmail.yandex.net (Yandex) with ESMTP id D5DB312BA for ; Fri, 1 May 2015 23:04:41 +0300 (MSK) Received: from smtp3o.mail.yandex.net (localhost [127.0.0.1]) by smtp3o.mail.yandex.net (Yandex) with ESMTP id A5AD71E2BD6 for ; Fri, 1 May 2015 23:04:41 +0300 (MSK) Received: from unknown (unknown [89.204.135.16]) by smtp3o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id ojjj9EOxtw-4esi7Txj; Fri, 1 May 2015 23:04:40 +0300 (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1430510681; bh=YIiMowNAp9D0Vw6FTV3nf7W7ZXb+/2u9PYsGyF4J2RY=; h=Date:From:To:Subject:Message-ID:References:In-Reply-To: Mail-Followup-To:User-Agent:MIME-Version:Content-Type: Content-Transfer-Encoding; b=uBCek0MbQ6uU88s5u6JLFyuLJB5nN3SY7NXUxB1nBpNziI3DKza2ftQh4Vo9aS5o3 9Owh5gwI5hNvq9SFkvho7UN6xoZ6v0UpkQWBOwjJwrYMoGelBEZG+CM2yI1tS3L6dx bW+vJzhAXksHwKo8cLaNf52Ds78T80dTl1XkUsog= Authentication-Results: smtp3o.mail.yandex.net; dkim=pass header.i=@yandex.com Date: Fri, 01 May 2015 22:04:34 +0200 From: Steffen Nurpmeso To: discuss@mdocml.bsd.lv Subject: Re: Redux: linking in mdoc(7)? Message-ID: <20150501200434.DOdMf7wQvHU=%sdaoden@yandex.com> References: <55424D7F.1010309@bsd.lv> <20150430173158.5wxc3dP2UnA=%sdaoden@yandex.com> <5542B58F.50608@bsd.lv> In-Reply-To: <5542B58F.50608@bsd.lv> Mail-Followup-To: discuss@mdocml.bsd.lv User-Agent: s-nail v14.7.11-414-g41649a5 X-Mailinglist: mdocml-discuss Reply-To: discuss@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Happy 1st of May :o, Kristaps Dzonsons wrote: |with the existing (and many) Texinfo and DocBook documents, both of |which allow and use intra-document linking. =20 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 Date: 2015-05-01 21:51:10 +0200 FIXME [mdocmx] Add ".Mx -ix [CAT]=A0KEY" 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=3D1). ..... Freely definable anchors and references[15] Via the =91.Mx -ix category key=92 and =91.Mx -ix key=92 usage forms ancho= rs can be defined almost anywhere, e.g., =91.Mx -ix subsubsection "An interesting topic"=92 defines the anchor =91An interesting topic=92 for the =93key=94 =91subsubsection=92. The form without a specified category will use the builtin name =91ixsx=92 instead. References to anchors[57] that have been created via -ix can be made by activating the .Sx search extension via =91.Mx -sx category=92 (or =91.Mx = -sx=92 for the builtin =91ixsx=92 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 =93normal=94 text so that they c= an be attached to something =93physical=94. --steffen -- To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv