doctools::idx::export::text - plain text export plugin
This package implements the doctools keyword index export plugin for the generation of plain text markup.
This is an internal package of doctools, for use by the higher level management packages handling keyword indices, especially doctools::idx::export, the export manager.
Using it from a regular interpreter is possible, however only with contortions, and is not recommended. The proper way to use this functionality is through the package doctools::idx::export and the export manager objects it provides.
The API provided by this package satisfies the specification of the docidx export plugin API version 2.
This command takes the canonical serialization of a keyword index, as specified in section Keyword index serialization format, and contained in serial, the configuration, a dictionary, and generates plain text markup encoding the index. The created string is then returned as the result of the command.
The text export plugin recognizes the following configuration variables and changes its behaviour as they specify.
This standard configuration variable contains a dictionary mapping from the symbolic files names in manpage references to the actual filenames and/or urls to be used in the output.
Url references and symbolic file names without a mapping are used unchanged.
Note that this plugin ignores the standard configuration variables user, file, and format, and their values.
Here we specify the format used by the doctools v2 packages to serialize keyword indices as immutable values for transport, comparison, etc.
We distinguish between regular and canonical serializations. While a keyword index may have more than one regular serialization only exactly one of them will be canonical.
An index serialization is a nested Tcl dictionary.
This dictionary holds a single key, doctools::idx, and its value. This value holds the contents of the index.
The contents of the index are a Tcl dictionary holding the title of the index, a label, and the keywords and references. The relevant keys and their values are
The value is a string containing the title of the index.
The value is a string containing a label for the index.
The value is a Tcl dictionary, using the keywords known to the index as keys. The associated values are lists containing the identifiers of the references associated with that particular keyword.
Any reference identifier used in these lists has to exist as a key in the references dictionary, see the next item for its definition.
The value is a Tcl dictionary, using the identifiers for the references known to the index as keys. The associated values are 2-element lists containing the type and label of the reference, in this order.
Any key here has to be associated with at least one keyword, i.e. occur in at least one of the reference lists which are the values in the keywords dictionary, see previous item for its definition.
The type of a reference can be one of two values,
The identifier of the reference is interpreted as symbolic file name, referring to one of the documents the index was made for.
The identifier of the reference is interpreted as an url, referring to some external location, like a website, etc.
The canonical serialization of a keyword index 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 the keyword index.
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.
The references listed for each keyword of the index, if any, are listed in ascending dictionary order of their labels, as generated by Tcl's builtin command lsort -increasing -dict.
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. 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.
Text formatter plugin
Copyright © 2009-2019 Andreas Kupries <andreas_kupries@users.sourceforge.net>