doctoc_intro(3tcl)

✨ doctoc_intro β€” the intro, bestie edition ✨

okay so real quick: this is doctoc_intro, and it lives in the Documentation tools manual (section 3tcl). it's the lil "hey come sit with me" page before you dive into the actual doctoc docs. grab a snack πŸ“


πŸ’– NAME πŸ’–

doctoc_intro β€” literally just the doctoc introduction, no cap


🌸 DESCRIPTION 🌸

so doctoc is short for documentation tables of contents, and it's not one single thing β€” it's a whole little friend group of related-but-different entities that work together so you can create and transform tables of contents for documentation, easily. the squad is:

  1. A tcl based language for the semantic markup of a table of contents. Markup is represented by Tcl commands.
  2. A package providing the ability to read and transform texts written in that markup language. It is important to note that the actual transformation of the input text is delegated to plugins.
  3. An API describing the interface between the package above and a plugin.

which of the more detailed documents you actually need depends on your role in the documentation process. main character energy, but for jobs πŸ’…

  1. A writer of documentation has to understand the markup language itself. A beginner to doctoc should read the more informally written doctoc language introduction first. Having digested this the formal doctoc language syntax specification should become understandable. A writer experienced with doctoc may only need the doctoc language command reference from time to time to refresh her memory.

While a document is written the dtp application can be used to validate it, and after completion it also performs the conversion into the chosen system of visual markup, be it *roff, HTML, plain text, wiki, etc. The simpler dtplite application makes internal use of doctoc when handling directories of documentation, automatically generating a proper table of contents for them.

  1. A processor of documentation written in the doctoc markup language has to know which tools are available for use.

The main tool is the aforementioned dtp application provided by Tcllib. The simpler dtplite does not expose doctoc to the user. At the bottom level, common to both applications, however sits the package doctoools::toc, providing the basic facilities to read and process files containing text in the doctoc format.

  1. At last, but not least, plugin writers have to understand the interaction between the doctools::toc package and its plugins, as described in the doctoc plugin API reference.

doctoc does not stand alone, it has two companion formats. These are called docidx and doctools, and they are for the markup of keyword indices, and general documentation, respectively. They are described in their own sets of documents, starting at the docidx introduction and the doctools introduction, respectively.

it's giving trio. it's giving destiny's child. each one has her own docs tho 🌈

😭 BUGS, IDEAS, FEEDBACK 😭

This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category doctools of the Tcllib Trackers [http://core.tcl.tk/tcllib/reportlist]. Please also report any ideas for enhancements you may have for either package and/or documentation.

When proposing code changes, please provide unified diffs, i.e the output of diff -u.

Note further that attachments are strongly preferred over inlined patches. Attachments can be made by going to the Edit form of the ticket immediately after its creation, and then using the left-most button in the secondary navigation bar.

fr fr, drop the diff as an attachment, the left-most button in that secondary nav bar is right there, iykyk 🫢

πŸŽ€ SEE ALSO πŸŽ€

  • docidx_intro
  • doctoc_lang_cmdref
  • doctoc_lang_faq
  • doctoc_lang_intro
  • doctoc_lang_syntax
  • doctoc_plugin_apiref
  • doctools::toc
  • doctools_intro

⭐ KEYWORDS ⭐

markup, semantic markup, table of contents, toc


πŸ‘‘ CATEGORY πŸ‘‘

Documentation tools


Copyright (c) 2007 Andreas Kupries <andreas_kupries@users.sourceforge.net>


and that's the whole page bestie, you ate it πŸ’…βœ¨ this came to you from the fine folks at tcllib, version 1.0 β€” k bye, go read doctoc_lang_intro next, mwah πŸŽ€πŸ¦‹πŸ’–

πŸ“¦ where this page comes from