1doctools::idx::import(n) Documentation tools doctools::idx::import(n)
2______________________________________________________________________________
6
8 doctools::idx::import - Importing keyword indices
9
11 package require doctools::idx::import ?0.2.1?
12 package require Tcl 8.4
14 package require struct::map
16 package require doctools::idx::structure
18 package require snit
20 package require pluginmgr
22 ::doctools::idx::import objectName
24 objectName method ?arg arg ...?
26 objectName destroy
28 objectName import text text ?format?
30 objectName import file path ?format?
32 objectName import object text object text ?format?
34 objectName import object file object path ?format?
36 objectName config names
38 objectName config get
40 objectName config set name ?value?
42 objectName config unset pattern...
44 objectName includes
46 objectName include add path
48 objectName include remove path
50 objectName include clear
52 IncludeFile currentfile path
54 import text configuration
56______________________________________________________________________________
58
60 This package provides a class to manage the plugins for the import of
61 keyword indices from other formats, i.e. their conversion from, for ex‐
62 ample docidx, json, etc.
63 This is one of the three public pillars the management of keyword in‐
65 dices resides on. The other two pillars are
66 [1] Exporting keyword indices, and
68 [2] Holding keyword indices
70 For information about the Concepts of keyword indices, and their parts,
72 see the same-named section. For information about the data structure
73 which is the major output of the manager objects provided by this pack‐
74 age see the section Keyword index serialization format.
75 The plugin system of our class is based on the package pluginmgr, and
77 configured to look for plugins using
78 [1] the environment variable DOCTOOLS_IDX_IMPORT_PLUGINS,
80 [2] the environment variable DOCTOOLS_IDX_PLUGINS,
82 [3] the environment variable DOCTOOLS_PLUGINS,
84 [4] the path "~/.doctools/idx/import/plugin"
86 [5] the path "~/.doctools/idx/plugin"
88 [6] the path "~/.doctools/plugin"
90 [7] the path "~/.doctools/idx/import/plugins"
92 [8] the path "~/.doctools/idx/plugins"
94 [9] the path "~/.doctools/plugins"
96 [10] the registry entry "HKEY_CURRENT_USER\SOFTWARE\DOCTOOLS\IDX\IM‐
98 PORT\PLUGINS"
99 [11] the registry entry "HKEY_CURRENT_USER\SOFTWARE\DOC‐
101 TOOLS\IDX\PLUGINS"
102 [12] the registry entry "HKEY_CURRENT_USER\SOFTWARE\DOCTOOLS\PLUGINS"
104 The last three are used only when the package is run on a machine using
106 Windows(tm) operating system.
107 The whole system is delivered with two predefined import plugins,
109 namely
110 docidx See docidx import plugin for details.
112 json See json import plugin for details.
114 Readers wishing to write their own import plugin for some format, i.e.
116 plugin writers reading and understanding the section containing the Im‐
117 port plugin API v2 reference is an absolute necessity, as it specifies
118 the interaction between this package and its plugins in detail.
119
121 [1] A keyword index consists of a (possibly empty) set of keywords.
122 [2] Each keyword in the set is identified by its name.
124 [3] Each keyword has a (possibly empty) set of references.
126 [4] A reference can be associated with more than one keyword.
128 [5] A reference not associated with at least one keyword is not pos‐
130 sible however.
131 [6] Each reference is identified by its target, specified as either
133 an url or symbolic filename, depending on the type of reference
134 (url, or manpage).
135 [7] The type of a reference (url, or manpage) depends only on the
137 reference itself, and not the keywords it is associated with.
138 [8] In addition to a type each reference has a descriptive label as
140 well. This label depends only on the reference itself, and not
141 the keywords it is associated with.
142 A few notes
144 [1] Manpage references are intended to be used for references to the
146 documents the index is made for. Their target is a symbolic file
147 name identifying the document, and export plugins may replace
148 symbolic with actual file names, if specified.
149 [2] Url references are intended on the othre hand are inteded to be
151 used for links to anything else, like websites. Their target is
152 an url.
153 [3] While url and manpage references share a namespace for their
155 identifiers, this should be no problem, given that manpage iden‐
156 tifiers are symbolic filenames and as such they should never
157 look like urls, the identifiers for url references.
158
160 PACKAGE COMMANDS
161 ::doctools::idx::import objectName
162 This command creates a new import manager object with an associ‐
163 ated Tcl command whose name is objectName. This object command
164 is explained in full detail in the sections Object command and
165 Object methods. The object command will be created under the
166 current namespace if the objectName is not fully qualified, and
167 in the specified namespace otherwise.
168 OBJECT COMMAND
170 All objects created by the ::doctools::idx::import command have the
171 following general form:
172 objectName method ?arg arg ...?
174 The method method and its arg'uments determine the exact behav‐
175 ior of the command. See section Object methods for the detailed
176 specifications.
177 OBJECT METHODS
179 objectName destroy
180 This method destroys the object it is invoked for.
181 objectName import text text ?format?
183 This method takes the text and converts it from the specified
184 format to the canonical serialization of a keyword index using
185 the import plugin for the format. An error is thrown if no
186 plugin could be found for the format. The serialization gener‐
187 ated by the conversion process is returned as the result of this
188 method.
189 If no format is specified the method defaults to docidx.
191 The specification of what a canonical serialization is can be
193 found in the section Keyword index serialization format.
194 The plugin has to conform to the interface specified in section
196 Import plugin API v2 reference.
197 objectName import file path ?format?
199 This method is a convenient wrapper around the import text
200 method described by the previous item. It reads the contents of
201 the specified file into memory, feeds the result into import
202 text and returns the resulting serialization as its own result.
203 objectName import object text object text ?format?
205 This method is a convenient wrapper around the import text
206 method described by the previous item. It expects that object
207 is an object command supporting a deserialize method expecting
208 the canonical serialization of a keyword index. It imports the
209 text using import text and then feeds the resulting serializa‐
210 tion into the object via deserialize. This method returns the
211 empty string as it result.
212 objectName import object file object path ?format?
214 This method behaves like import object text, except that it
215 reads the text to convert from the specified file instead of be‐
216 ing given it as argument.
217 objectName config names
219 This method returns a list containing the names of all configu‐
220 ration variables currently known to the object.
221 objectName config get
223 This method returns a dictionary containing the names and values
224 of all configuration variables currently known to the object.
225 objectName config set name ?value?
227 This method sets the configuration variable name to the speci‐
228 fied value and returns the new value of the variable.
229 If no value is specified it simply returns the current value,
231 without changing it.
232 Note that while the user can set the predefined configuration
234 variables user and format doing so will have no effect, these
235 values will be internally overridden when invoking an import
236 plugin.
237 objectName config unset pattern...
239 This method unsets all configuration variables matching the
240 specified glob patterns. If no pattern is specified it will un‐
241 set all currently defined configuration variables.
242 objectName includes
244 This method returns a list containing the currently specified
245 paths to use to search for include files when processing input.
246 The order of paths in the list corresponds to the order in which
247 they are used, from first to last, and also corresponds to the
248 order in which they were added to the object.
249 objectName include add path
251 This methods adds the specified path to the list of paths to use
252 to search for include files when processing input. The path is
253 added to the end of the list, causing it to be searched after
254 all previously added paths. The result of the command is the
255 empty string.
256 The method does nothing if the path is already known.
258 objectName include remove path
260 This methods removes the specified path from the list of paths
261 to use to search for include files when processing input. The
262 result of the command is the empty string.
263 The method does nothing if the path is not known.
265 objectName include clear
267 This method clears the list of paths to use to search for in‐
268 clude files when processing input. The result of the command is
269 the empty string.
270
272 Plugins are what this package uses to manage the support for any input
273 format beyond the Keyword index serialization format. Here we specify
274 the API the objects created by this package use to interact with their
275 plugins.
276 A plugin for this package has to follow the rules listed below:
278 [1] A plugin is a package.
280 [2] The name of a plugin package has the form doctools::idx::im‐
282 port::FOO, where FOO is the name of the format the plugin will
283 generate output for. This name is also the argument to provide
284 to the various import methods of import manager objects to get a
285 string encoding a keyword index in that format.
286 [3] The plugin can expect that the package doctools::idx::ex‐
288 port::plugin is present, as indicator that it was invoked from a
289 genuine plugin manager.
290 [4] The plugin can expect that a command named IncludeFile is
292 present, with the signature
293 IncludeFile currentfile path
295 This command has to be invoked by the plugin when it has
296 to process an included file, if the format has the con‐
297 cept of such. An example of such a format would be do‐
298 cidx.
299 The plugin has to supply the following arguments
301 string currentfile
303 The path of the file it is currently processing.
304 This may be the empty string if no such is known.
305 string path
307 The path of the include file as specified in the
308 include directive being processed.
309 The result of the command will be a 5-element list con‐
311 taining
312 [1] A boolean flag indicating the success (True) or
314 failure (False) of the operation.
315 [2] In case of success the contents of the included
317 file, and the empty string otherwise.
318 [3] The resolved, i.e. absolute path of the included
320 file, if possible, or the unchanged path argument.
321 This is for display in an error message, or as the
322 currentfile argument of another call to Include‐
323 File should this file contain more files.
324 [4] In case of success an empty string, and for fail‐
326 ure a code indicating the reason for it, one of
327 notfound
329 The specified file could not be found.
330 notread
332 The specified file was found, but not be
333 read into memory.
334 [5] An empty string in case of success of a notfound
336 failure, and an additional error message describ‐
337 ing the reason for a notread error in more detail.
338 [5] A plugin has to provide one command, with the signature shown
340 below.
341 import text configuration
343 Whenever an import manager of doctools::idx has to parse
344 input for an index it will invoke this command.
345 string text
347 This argument will contain the text encoding the
348 index per the format the plugin is for.
349 dictionary configuration
351 This argument will contain the current configura‐
352 tion to apply to the parsing, as a dictionary map‐
353 ping from variable names to values.
354 The following configuration variables have a pre‐
356 defined meaning all plugins have to obey, although
357 they can ignore this information at their discre‐
358 tion. Any other other configuration variables rec‐
359 ognized by a plugin will be described in the man‐
360 page for that plugin.
361 user This variable is expected to contain the
363 name of the user owning the process invok‐
364 ing the plugin.
365 format This variable is expected to contain the
367 name of the format whose plugin is invoked.
368 [6] A single usage cycle of a plugin consists of the invokations of
370 the command import. This call has to leave the plugin in a state
371 where another usage cycle can be run without problems.
372
374 Here we specify the format used by the doctools v2 packages to serial‐
375 ize keyword indices as immutable values for transport, comparison, etc.
376 We distinguish between regular and canonical serializations. While a
378 keyword index may have more than one regular serialization only exactly
379 one of them will be canonical.
380 regular serialization
382 [1] An index serialization is a nested Tcl dictionary.
384 [2] This dictionary holds a single key, doctools::idx, and
386 its value. This value holds the contents of the index.
387 [3] The contents of the index are a Tcl dictionary holding
389 the title of the index, a label, and the keywords and
390 references. The relevant keys and their values are
391 title The value is a string containing the title of the
393 index.
394 label The value is a string containing a label for the
396 index.
397 keywords
399 The value is a Tcl dictionary, using the keywords
400 known to the index as keys. The associated values
401 are lists containing the identifiers of the refer‐
402 ences associated with that particular keyword.
403 Any reference identifier used in these lists has
405 to exist as a key in the references dictionary,
406 see the next item for its definition.
407 references
409 The value is a Tcl dictionary, using the identi‐
410 fiers for the references known to the index as
411 keys. The associated values are 2-element lists
412 containing the type and label of the reference, in
413 this order.
414 Any key here has to be associated with at least
416 one keyword, i.e. occur in at least one of the
417 reference lists which are the values in the key‐
418 words dictionary, see previous item for its defi‐
419 nition.
420 [4] The type of a reference can be one of two values,
422 manpage
424 The identifier of the reference is interpreted as
425 symbolic file name, referring to one of the docu‐
426 ments the index was made for.
427 url The identifier of the reference is interpreted as
429 an url, referring to some external location, like
430 a website, etc.
431 canonical serialization
433 The canonical serialization of a keyword index has the format as
434 specified in the previous item, and then additionally satisfies
435 the constraints below, which make it unique among all the possi‐
436 ble serializations of the keyword index.
437 [1] The keys found in all the nested Tcl dictionaries are
439 sorted in ascending dictionary order, as generated by
440 Tcl's builtin command lsort -increasing -dict.
441 [2] The references listed for each keyword of the index, if
443 any, are listed in ascending dictionary order of their
444 labels, as generated by Tcl's builtin command lsort -in‐
445 creasing -dict.
446
448 This document, and the package it describes, will undoubtedly contain
449 bugs and other problems. Please report such in the category doctools
450 of the Tcllib Trackers [http://core.tcl.tk/tcllib/reportlist]. Please
451 also report any ideas for enhancements you may have for either package
452 and/or documentation.
453 When proposing code changes, please provide unified diffs, i.e the out‐
455 put of diff -u.
456 Note further that attachments are strongly preferred over inlined
458 patches. Attachments can be made by going to the Edit form of the
459 ticket immediately after its creation, and then using the left-most
460 button in the secondary navigation bar.
461
463 conversion, docidx, documentation, import, index, json, keyword index,
464 manpage, markup, parsing, plugin, reference, url
465
467 Documentation tools
468
470 Copyright (c) 2009-2019 Andreas Kupries <andreas_kupries@users.sourceforge.net>
471tcllib 0.2.1 doctools::idx::import(n)