When creating a two-level index, it is quite common to have no page numbers for the top level, for example:
Widgits
Blue 20, 29
Green 104, 105
Red 93, 94
In H&M, it seems that the top level always has page numbers, even if that keyword was never mentioned on its own in any topic. It's usually the page numbers of the first 2nd-level entry, so in the above example H&M would produce:
Widgits 20, 29
Blue 20, 29
Green 104, 105
Red 93, 94
Is there any way to stop this?
Two-level keyword index: can't stop page numbers on top lvl
Moderators: Alexander Halser, Tim Green
- Alexander Halser
- EC-Software Support
- Posts: 4105
- Joined: Mon Jun 24, 2002 7:24 pm
- Location: Salzburg, Austria
- Contact:
>>Is there any way to stop this?
No, not yet. Sorry. The top level keywords always have page numbers as well. But there is another glitch that has to do with the keyword index in help files: to make two-level keywords work properly, you must define the master keyword separately and then repeat it with the second-level keyword. Example:
Widgits
Widgits, Blue
Widgits, Green
Widgits, Red
If the first Widgits is missing, the keyword index may not be sorted correctly in the compiled help file. But the first Widgits now is a keyword on it's own which will in any case have a page number...
No, not yet. Sorry. The top level keywords always have page numbers as well. But there is another glitch that has to do with the keyword index in help files: to make two-level keywords work properly, you must define the master keyword separately and then repeat it with the second-level keyword. Example:
Widgits
Widgits, Blue
Widgits, Green
Widgits, Red
If the first Widgits is missing, the keyword index may not be sorted correctly in the compiled help file. But the first Widgits now is a keyword on it's own which will in any case have a page number...
Alexander Halser
Senior Software Architect, EC Software GmbH
Senior Software Architect, EC Software GmbH