Re: indexing

[Trevor Daniels]

Ralph Palmer wrote Tuesday, August 19, 2008 2:29 PM

> I think it would be helpful to have a better description of the indexes,
> what's being indexed, and what the indexes do/are.

Agreed.  Indexes are important.  Here is my view of what they
should contain.

> Specifically:
>
>   1. Are all the entries in the command index duplicated in the regular
>   index?

The command index contains just the @funindex
entries, but the general index contains both @funindex and @cindex
entries.   This happens automatically.

>   2. In the regular index, what's the significance of the colon? What is
>   the text before the colon? After the colon?

The link before the colon is to the precise point of the index entry.

The link after the colon is to the start of the section containing the
index entry.

>   3. What's the significance of bold vs. normal font in the entries?

I don't think it's bold vs normal, rather monospaced vs proportional?
The monospaced entries are those in @code{ ...}, which should be
used for LilyPond notation - commands and keywords.

> Are these clear to everyone (besides me, that is)? Would it be difficult 
> to
> add descriptions?

How about these:

> Appendix E LilyPond command index

This index lists all the LilyPond commands and keywords and
provides links to those sections of the manual which describe or
discuss their use.

> Appendix F LilyPond index

In addition to the LilyPond commands and keywords, this index
provides links to the manual based on musical terms and on
descriptions of the LilyPond commands and keywords.

> Ralph

Trevor