[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Window Definitions in Context-Sensitive Help
Dear Ian Thanks very much for your thoughts on the CSH proposals, and in
particular your thoughts on window definitions. I’ve copied the DITA Help
Subcommittee list on this reply, because I think it is of broad interest and
needs discussion. If you could have more than one window definition in a map,
wouldn’t that provide a pathway to all the HTML Help options? To a large
extent, the map in DITA has to be the container for the information that might
be stored in an HHP project file in an HTML Help project. There isn’t any other
project container. (Of course, it may be possible that we need a project
container, but I can’t see a strong argument for one at the moment.) With regard to the context hooks (context identification names
and numbers) being scattered through the ditamap, I think the way we should
look at it is whether the storage of the information is semantically and
logically correct, rather than whether it is easy to read. A tool will
presumably make the allocation of the hooks easy. For scenarios where the hooks
are specific to the map (that is, a topic needs to have different hooks in
different publishing contexts), it would seem that a direct reference (where
the hook is stored within the topicref element) is a better approach than
indirect, where the hooks are stored apart in something like a reltable. That
approach also provides some sort of “cascade” options where topics with hooks
stored within the topic metadata could also be drawn up into the context map
file. Does anyone else have some thoughts on the matter?
Tony Self From: ian balanza-davis
[mailto:ibalanza_davis@yahoo.co.uk] Hi
Tony |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]