Thanks so much for implementing this!  I can get rid of the hacks I had and
make use of it in other docs.

I did use this new version to generate Maxima's manual in pdf.  The index
entries and subentries look fine for the most part, but there are a few
oddities.  I don't know if I messed up or if it's a bug in texinfo.  When I
isolate the problem, I'll let you know.

But in general it looks fantastic!  And much better than the hack I was
using!


On Sun, Apr 28, 2019 at 2:20 AM Gavin Smith <gavinsmith0...@gmail.com>
wrote:

> On Sun, Apr 28, 2019 at 02:33:25AM -0600, arn...@skeeve.com wrote:
> > Gavin Smith <gavinsmith0...@gmail.com> wrote:
> >
> > > On Sat, Mar 02, 2019 at 04:33:30PM +0000, Gavin Smith wrote:
> > > > Implemented as @subentry in git commit 372cfab.
> > > >
> > > > A test file is attached. Please feel free to experiment.
> > > >
> > > > It still needs to be implemented in texi2any, once the syntax is
> > > > finalised. Volunteers are welcome.
> > >
> > > I've added some support for @seeentry and @seealso in index entries in
> > > texi2any.  They are ignored except for DocBook output.
> >
> > Truly awesome!!!
> >
> > How do mean "ignored"?  Do you simply remove the @subentry and use
> > the rest of the line as the index text, in Info, for example?
>
> I mean entries with @seeentry and @seealso do not add any index entries
> for HTML and Info output.  @subentry isn't ignored.
>
> > I'd suggest something like  s/ *@subentry +/, /g   in sed syntax
> > for Info, if that makes sense to you.
>
> In HTML and Info output, this is what is done already - the parts are
> separated by commas.
>
> > And once again, a huge THANK YOU for working with me to add this feature
> > to Texinfo.  I have been working on the gawk manual's index to take
> > advantage of this and it makes for an incredible improvement.
>
> That is very good to hear.  Thank you for suggesting the new features
> and working to implement them in texindex.  I'm sure others will find
> them useful too.
>
>

-- 
Ray

Reply via email to