From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from forward3h.cmail.yandex.net (forward3h.cmail.yandex.net [87.250.230.18]); by fantadrom.bsd.lv (OpenSMTPD) with ESMTP id aec6b9d5; for ; Tue, 5 May 2015 08:47:23 -0500 (EST) Received: from smtp3o.mail.yandex.net (smtp3o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::27]) by forward3h.cmail.yandex.net (Yandex) with ESMTP id D17F91A7C for ; Tue, 5 May 2015 16:47:19 +0300 (MSK) Received: from smtp3o.mail.yandex.net (localhost [127.0.0.1]) by smtp3o.mail.yandex.net (Yandex) with ESMTP id 9320E1E3815 for ; Tue, 5 May 2015 16:47:19 +0300 (MSK) Received: from unknown (unknown [89.15.237.192]) by smtp3o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id SOURKI4deD-lIcC2oqq; Tue, 5 May 2015 16:47:18 +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=1430833638; bh=lBaixb9iS7yFkW5PdmLT/I6bZ8bU2r8dCYAzWwpJHuE=; h=Date:From:To:Subject:Message-ID:References:In-Reply-To: Mail-Followup-To:User-Agent:MIME-Version:Content-Type: Content-Transfer-Encoding; b=ko7s0RxN/diUhRMEE/6inT+UoxhcBGpTJGEAfkYVCvJEvdAOeH6w+jvnugXuCdvhl mB3Wwvv/HGrP2/E2cNIb8i1HdA9gogzE71F2p8PjNS08O3tO6W3+CyiPzbZg8s8Ncb W3HgTOM6gJKaJEfxZDDKC1Q1bbxN5RZJ9yyinZR4= Authentication-Results: smtp3o.mail.yandex.net; dkim=pass header.i=@yandex.com Date: Tue, 05 May 2015 15:47:14 +0200 From: Steffen Nurpmeso To: discuss@mdocml.bsd.lv Subject: Re: Redux: linking in mdoc(7)? Message-ID: <20150505134714.yhPAIfZcwj8BIIoZwMCiZQ==@yandex.com> References: <55424D7F.1010309@bsd.lv> <20150430173158.5wxc3dP2UnA=%sdaoden@yandex.com> <5542B58F.50608@bsd.lv> <20150501200434.DOdMf7wQvHU=%sdaoden@yandex.com> In-Reply-To: <20150501200434.DOdMf7wQvHU=%sdaoden@yandex.com> Mail-Followup-To: discuss@mdocml.bsd.lv User-Agent: s-nail v14.8.0-10-g6fd1f69 X-Mailinglist: mdocml-discuss Reply-To: discuss@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable FYI, i've completed the mdocmx(7) side of the road. Ciao. Freely definable anchors and references[15] Via the =E2=80=98.Mx -ix category key=E2=80=99 and =E2=80=98.Mx -ix key= =E2=80=99 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., =E2=80=98.Mx -ix subsubsection "An int= eresting topic"=E2=80=99 defines the anchor =E2=80=98An interesting topic=E2=80= =99 for the =E2=80=9Ckey=E2=80=9D =E2=80=98subsubsection=E2=80=99. The form without a specified category = will use the builtin name =E2=80=98ixsx=E2=80=99 instead. References to anchors that have been created via -ix can be made by acti= =E2=80=90 vating the .Sx search extension via =E2=80=98.Mx -sx category=E2=80=99 (= or =E2=80=98.Mx -sx=E2=80=99 for the builtin =E2=80=98ixsx[58]=E2=80=99 category) followed by a normal lo= cal 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 =E2=80=9Cnormal=E2=80=9D te= xt so that they can be attached to something =E2=80=9Cphysical=E2=80=9D. --steffen -- To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv