I would appreciate some insight about the plans for future development.
Specifically, are there plans to integrate the functionality offered
in Amaya back into ThotEditor (fetching/storing documents on the web,
on the fly conversion of HTML files on input...).
Indeed, many of my documents are currently in LaTeX and converted to
HTML through latex2html. I will probably convert these to Thot
rather easily. Another part of my documents are HTML files referencing
source code header files (Modula-3 interfaces). The header files
contain HTML documentation in their comments and the web server converts
these to complete HTML files on the fly. Thus, the complete documentation
for source code libraries is available on line and partly extracted from
the commented header files.
If there was an easy mechanism in Thot to import different file formats,
i could use this to translate to LaTeX or Postscript complete reference
manuals, using the Thot translation facilities along with "inclusion"
- A nice document "manual" is created with ThotEditor containing the
documentation body and "inclusion" references to the source code
header files (header.h).
- The document is saved as HTML (manual.html). Equations, inclusion
references and other constructs not supported by HTML are encoded
as the closest HTML tag with added attributes
(e.g. <A HREF="..." CLASS=ThotIncludeReference>).
- Someone else could edit manual.html using other HTML tools as long as
they are careful about the special attributes.
- Manual.html could also be read back into Thot without any loss of
- Similarly, the header files could be read into Thot (converted on input
and translated back on output), given a suitable Thot schema.
- Through a suitable translation, processing the "inclusion" references,
it would be possible to print the complete reference manual.
I can easily build all the tools for "converting" the source files
and HTML manual. I would however like to use a clean "generic" import
mechanism, not unlike the excellent "translate" facilities
available for export. This could have numerous applications like
handling "natively" SGML documents (given corresponding DTD and schemas),
structured editing of source code...