On 3/1/19, Gavin Smith wrote:
> Whatever output is chosen, it would be good to check how existing
> versions of texindex deal with it: we should avoid completely breaking
> them if at all possible.
So awk texindex, given the input indextab.cp:
\entry{one}{1}{one}
\entry{one\subind two}{1}{one}{t
On Fri, Mar 01, 2019 at 02:25:29AM -0700, arn...@skeeve.com wrote:
> > Maybe a special marker character could be output that texindex treats
> > specially: e.g. the above would be output as
> >
> > \entry{aa^_a}{1}{aa}{a}
> > \entry{aa^_z}{3}{aa}{z}
> > \entry{aah}{5}{aah}
> >
> > where ^_ is a 0x
On Fri, Mar 01, 2019 at 02:25:29AM -0700, arn...@skeeve.com wrote:
>
> @indent makes sense, since that's what happens on the page, but I
> can live with @tab also, or something like @subind might be good too.
> I don't have strong feelings, as long as it makes reasonable sense
> and is easy to con
Hi.
> * What happens if there is an index entry with no secondary term and an
> identical index entry with a secondary term, e.g.
>
> @cindex foo
> @cindex foo @sub bar
>
> I think that both should be kept. When I tested it with C texindex, one
> of them was lost in the output.
I agree. We nee
