| 1. Making it possible to reference the <command> tag: I have requested
this myself. It is not a really an online-doctype specific item;
it will require changs to the tag translator and global tag
definitions.
2. Making it easier to process one chapter: no one has more sympathy
for you than I! But it's not an easy problem and requires a lot
more thought and, I suspect, changes to the DOCUMENT command line
and other features. It's definitely on the wishlist.
To process a single element, I use a template with all the frontmatter/
title page/contents, etc. stuff in it. If you use the /INCLUDE=
qualifier you don't have to go in and alter the source file.
Note, too, that the <index_file> tag need not be at the end of the
file. It can be anywhere and can be part of your template. This
is not a terrific solution, granted, but may be a bit easier than
what you've been doing.
Thanks,
Mary
|
|
> 1. Making it possible to reference the <command> tag: I have requested
> this myself. It is not a really an online-doctype specific item;
> it will require changs to the tag translator and global tag
> definitions.
Has there been any progress on this? One of the books I'm converting
is a 600+ page reference book which consists solely of functions,
described alphabetically. It is very annoying to the reader to see
another function referenced, and to have to go either to the contents
section or the index in order to read about the other function.
I would also like to extend the request to make it possible to
reference <description> tags within a <command> section. The
descriptions of some functions are sometimes quite lengthy, and contain
the following sections:
Syntax
Description
Parameters
Qualifiers
Examples
Special Features and Restrictions
It would be nice to be able to reference information in, say, the
section on special features and restrictions from, say, the general
description section.
Ever hopeful,
Ro
|