From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 24010 invoked from network); 26 Mar 2022 09:25:53 -0000 Received: from bsd.lv (HELO mandoc.bsd.lv) (66.111.2.12) by inbox.vuxu.org with ESMTPUTF8; 26 Mar 2022 09:25:53 -0000 Received: from fantadrom.bsd.lv (localhost [127.0.0.1]) by mandoc.bsd.lv (OpenSMTPD) with ESMTP id ca816816 for ; Sat, 26 Mar 2022 04:25:48 -0500 (EST) Received: from scc-mailout-kit-02.scc.kit.edu (scc-mailout-kit-02.scc.kit.edu [129.13.231.82]) by mandoc.bsd.lv (OpenSMTPD) with ESMTP id 53473529 for ; Sat, 26 Mar 2022 04:25:46 -0500 (EST) Received: from hekate.asta.kit.edu ([2a00:1398:5:f401::77]) by scc-mailout-kit-02.scc.kit.edu with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (envelope-from ) id 1nY2g5-008Gth-5d; Sat, 26 Mar 2022 10:25:45 +0100 Received: from login-1.asta.kit.edu ([2a00:1398:5:f400::72]) by hekate.asta.kit.edu with esmtp (Exim 4.94.2) (envelope-from ) id 1nY2g3-003vpG-BE; Sat, 26 Mar 2022 10:25:43 +0100 Received: from schwarze by login-1.asta.kit.edu with local (Exim 4.92) (envelope-from ) id 1nY2g3-0005Uo-Nk; Sat, 26 Mar 2022 10:25:43 +0100 Date: Sat, 26 Mar 2022 10:25:43 +0100 From: Ingo Schwarze To: mario.blaettermann@gmail.com Cc: discuss@mandoc.bsd.lv Subject: Re: HTML output: section headers with diacritics not in table of contents Message-ID: References: X-Mailinglist: mandoc-discuss Reply-To: discuss@mandoc.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Hi Mario, Jan Stary wrote on Fri, Mar 25, 2022 at 10:20:30PM +0100: > On Mar 25 21:59:26, mario.blaettermann@gmail.com wrote: >> Am Fr., 25. März 2022 um 21:36 Uhr schrieb Jan Stary : >>> On Mar 25 17:57:21, mario.blaettermann@gmail.com wrote: >>>>> Regarding -O toc, you should be aware that a number of senior OpenBSD >>>>> developers hated the feature so much that i disabled it completely >>>>> on man.openbsd.org. They argue the feature is superfluous, noisy, >>>>> and the whole idea of prefixing a TOC to a manual page is misguided. >>>> To mention, the TOC works at man.openbsd.org, for example: >>>> http://man.openbsd.org/mandoc#Syntax_tree_output >>> I don't see a TOC on that page. >> What you've expected is probably a TOC like [1]. > Yes, because that's what mandoc calls a TOC: > > toc If an input file contains at least two non-standard sections, > print a table of contents near the beginning of the output. Exactly. To see what a "TABLE OF CONTENTS" (TOC) is, please look at https://man.bsd.lv/pf.conf.5 where i just enabled TOCs for demonstrational purposes and compare that page to https://man.openbsd.org/pf.conf.5 where TOCs are disabled. The mandoc(1) page never gets a TOC because it does not contain two custom sections (in fact, not even one). >> But the TOC generated >> by Mandoc doesn't mean a real table of contents in this case, it's >> merely a »hidden« TOC, which enables to click on section headers and >> options to generate hyperlinks for that position. If you can open the >> link mentioned above, and »Syntax tree output« is on top of the page >> displayed in the browser, then this kind of TOC works. >> [1] https://archlinux.org/pacman/makepkg.8.html > I think these are 'tags' in the mandoc parlance. > http://man.openbsd.org/mandoc#tag Exactly, and that mandoc(1) terminology is motivated by this pre-existing terminology: https://man.openbsd.org/less.1#T https://man.openbsd.org/ctags.1 Yours, Ingo -- To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv