Re: Feature request: multilevel indexing for TeX

[arnold]

Gavin Smith <address@hidden> wrote:

> On Mon, Mar 04, 2019 at 12:34:42AM -0700, address@hidden wrote:
> > No. As per the mail you discovered, Karl just said "make it work with both"
> > so I did. But we're five years later, let's just make the change, please.
>
> Made in commit 2405caa.

Awesome!

> texindex should continue to recognize \ as the escape character for
> compatibility with old versions of texinfo.tex.

OK. It complicates things some, but not terribly.

> > > > Or we could go with keywords, to ensure that the user gets what they
> > > > wanted:
> > > >
> > > >         @cindex espresso makers @see{coffee makers}
> > > >         @cindex coffee @seealso{instant coffee}
> > >
> > > I think keywords are the way to go here.
> > 
> > All sounds good.  I will assume that if the second entry doesn't
> > have a number in it that it's a "see" or "see also" entry and
> > treat it approriately.
> > 
> > Hmm. Do we ever get roman numerals in the number field of an entry?
>
> I tested it and yes, this can happen.

OK. No problem. The number field must match /^([ivxdlcm]+|([0-9]+)$/
to be a number. Otherwise it's a see/see also.

> Is the "see also" feature something that anybody 
> wants or is it just theoretical?

I want it. The gawk manual has both See and See Also in its index.

Hmm... Here are two entries in the current manual:

        @cindex output record separator, See @code{ORS} variable
        @cindex @code{print} statement, See Also address@hidden of output

I guess these become:

        @cindex output record separator @address@hidden variable}
        @cindex @code{print} statement @address@hidden of output}

(Can texinfo.tex add back the comma before the @see/@seealso?)

Leading to:

        @entry{output record separator, See ORS variabale}{}{output record 
separator @address@hidden variable}}
        @entry{print statement, See Also redirection, of address@hidden 
statement @address@hidden of output}}

Thoughts?

Thanks!

Arnold