doctools:...port::text(3tcl)

πŸ“¦
version 2.0 Β· 2 versions
, in debian trixie, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– NAME πŸ’–

doctools::toc::export::text β€” bestie, this is the plain text export plugin. That's it, that's the whole vibe. ✨

(Oh and hey, you're reading the doctools manual page from the Documentation tools collection, doctools:...port::text(3tcl). Hiii. 🫢)


🌸 SYNOPSIS 🌸

package require Tcl 8.5 9

package require doctools::toc::export::text ?0.2?

package require doctools::text

export serial configuration

✨ DESCRIPTION ✨

Okay so listen. This package implements the doctools table of contents export plugin, and its whole job is generating plain text markup. Iconic, honestly. πŸ’…

It's an internal package of doctools, meaning it's built to be used by the higher level management packages that handle tables of contents β€” especially doctools::toc::export, the export manager. Like, that's its whole social circle.

Now, technically you could use it straight from a regular interpreter, but only with contortions, and it is not recommended. Do not do this to yourself. 😭 The proper way to use this functionality is through the package doctools::toc::export and the export manager objects it provides. That's the main character path. πŸ‘‘

🌈 API 🌈

The API this package gives you satisfies the specification of the doctoc export plugin API version 2. No cap. ⭐

  • export serial configuration β€” this command takes the canonical serialization of a table of contents (specified over in the ToC serialization format section, you'll get there), and it's contained in serial. Also takes the configuration, which is a dictionary. Then it generates plain text markup encoding that table, and the created string is returned as the result of the command. Slay. πŸŽ€

πŸ¦‹ CONFIGURATION πŸ¦‹

The text export plugin recognizes the following configuration variables and changes its behaviour as they specify. She's flexible like that. πŸ’œ

  • dictionary map β€” this standard configuration variable contains a dictionary mapping from the (symbolic) document ids in reference entries to the actual filenames and/or urls to be used in the output.

Document ids without a mapping are used unchanged. Fr fr.

Heads up bestie: this plugin ignores the standard configuration variables user, file, and format, and their values. Not her problem, not her business. πŸ™ˆ

πŸ“ TOC SERIALIZATION FORMAT πŸ“

Here we specify the format used by the doctools v2 packages to serialize tables of contents as immutable values for transport, comparison, etc. Immutable. Frozen. Locked in. 🧊

We distinguish between regular and canonical serializations. While a table of contents may have more than one regular serialization, only exactly one of them will be canonical. There can be only one. πŸ‘‘

🌟 regular serialization 🌟

  1. The serialization of any table of contents is a nested Tcl dictionary.
  2. This dictionary holds a single key, doctools::toc, and its value. This value holds the contents of the table of contents.
  3. The contents of the table of contents are a Tcl dictionary holding the title of the table of contents, a label, and its elements. The relevant keys and their values are:
    • title β€” the value is a string containing the title of the table of contents.
    • label β€” the value is a string containing a label for the table of contents.
    • items β€” the value is a Tcl list holding the elements of the table, in the order they are to be shown.

Each element is a Tcl list holding the type of the item, and its description, in this order. An alternative description would be that it is a Tcl dictionary holding a single key β€” the item type β€” mapped to the item description.

The two legal item types and their descriptions are:

  • reference β€” this item describes a single entry in the table of contents, referencing a single document. To this end its value is a Tcl dictionary containing an id for the referenced document, a label, and a longer textual description which can be associated with the entry. The relevant keys and their values are:
    • id β€” the value is a string containing the id of the document associated with the entry.
    • label β€” the value is a string containing a label for this entry. This string also identifies the entry, and no two entries (references and divisions) in the containing list are allowed to have the same label. So don't even try it. πŸ’€
    • desc β€” the value is a string containing a longer description for this entry.
  • division β€” this item describes a group of entries in the table of contents, inducing a hierarchy of entries. To this end its value is a Tcl dictionary containing a label for the group, an optional id to a document for the whole group, and the list of entries in the group. The relevant keys and their values are:
    • id β€” the value is a string containing the id of the document associated with the whole group. This key is optional.
    • label β€” the value is a string containing a label for the group. This string also identifies the entry, and no two entries (references and divisions) in the containing list are allowed to have the same label. Same rule, same energy. 🚫
    • items β€” the value is a Tcl list holding the elements of the group, in the order they are to be shown. This list has the same structure as the value for the keyword items used to describe the whole table of contents, see above. This closes the recursive definition of the structure, with divisions holding the same type of elements as the whole table of contents, including other divisions. It's turtles all the way down, bestie. 🐒

πŸ’« canonical serialization πŸ’«

The canonical serialization of a table of contents has the format as specified in the previous item, and then additionally satisfies the constraints below, which make it unique among all the possible serializations of this table of contents. Unique queen behaviour. πŸ‘‘

  1. The keys found in all the nested Tcl dictionaries are sorted in ascending dictionary order, as generated by Tcl's builtin command lsort -increasing -dict.

😭 BUGS, IDEAS, FEEDBACK 😭

This document, and the package it describes, will undoubtedly contain bugs and other problems. We're being honest here. Ngl. πŸ™ˆ 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 β€” we want them, genuinely. 🫢

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. Yes, that one. That exact button. ✨


πŸ’œ KEYWORDS πŸ’œ

doctools, export, plain text, serialization, table of contents, toc


πŸ‘‘ CATEGORY πŸ‘‘

Text formatter plugin


Copyright (c) 2009-2019 Andreas Kupries <andreas_kupries@users.sourceforge.net>


And that's the whole page bestie, tysm for reading πŸ₯° this absolute gem comes to you from tcllib, version 0.2, and yeah the header/footer were giving doctools:...port::text(3tcl) the whole time β€” mwah, go ship something cute. πŸ’…βœ¨πŸ’–

πŸ“¦ where this page comes from