texinfo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: report with biggest nodes


From: Karl Berry
Subject: Re: report with biggest nodes
Date: Tue, 17 Jan 2012 16:23:08 -0800

    expect that users do the right thing.

If we give authors an easy way to avoid doing work, they will avoid it.
To the detriment of the manual.

    1. Generate missing nodes and menu entries when generating the output,
       by adding them to the tree after parsing (approximately when figuring 
       out the structure of the document).

Sure.  That can only help with error recovery, etc.

    2. outside of texi2any, code a tool that rewrites Texinfo code, adding
       missing nodes and menu entries.

If users run that tool and then work with the output, that seems ok by
me.  It is in effect what the related texinfo-mode commands do now, anyway.

I had been imagining something else: that we would simply silently
accept the deficient manuals and correct the problems on the fly, so
that authors never have to think about it.  That's what I was having
problems with.

    This is already what is done

Yep.

     (though this may be errors and not warnings), 

So much the better.

    I am pretty sure that we already discussed about it more than once.  

Indeed.  Sometimes you just have to tell me I'm totally confused :).
Sometimes, like rms, I just forget we've already had lengthy discussions
on some issue XYZ when it comes up in a slightly new context so that I
don't recognize it :(.

    also as part of having stuff done by emacs available out of emacs.  

Ack.

    pod2texi translator (did I announce that I did that translator?)

No.  That is great news!  Does it work with, e.g., the base perl pods?
Or the parallel.pod from GNU Parallel?
Is it checked in?  If so, I guess I missed it.

If it's ready, we should incorporate it into 5.0.

    automatic node/menu generation, I have to add anchors like
      @section My section
      @anchor{My section}

I don't understand, why not @node My section?  But whatever works, I'm
sure you did what is needful.

    while waiting for the release, 

Sorry I am so slow.

    tests cleanups and enhancements, and
    preparing for the automatic generation of nodes and menus...

Ack.

Thanks,
k



reply via email to

[Prev in Thread] Current Thread [Next in Thread]