bug-texinfo
[Top][All Lists]
Advanced

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

Re: @menu puts too many restrictions to produce the .info file


From: Gavin Smith
Subject: Re: @menu puts too many restrictions to produce the .info file
Date: Tue, 27 Oct 2020 15:55:35 +0000
User-agent: Mutt/1.9.4 (2018-02-28)

On Tue, Oct 27, 2020 at 05:19:50PM +0200, Eli Zaretskii wrote:
> > Date: Tue, 27 Oct 2020 09:40:35 +0100
> > From: Patrice Dumas <pertusus@free.fr>
> > 
> > Ok.  The more I think about it, the more I agree that it should be left
> > that way, ie that novalidate only cares about errors that are real 
> > errors in every case, not errors of consistency.  This means that the
> > "Pointer Validation" node should be modified to separate what
> > novalidate checks, I think it is only the point 1:
> > 
> >   1. If a 'Next', 'Previous', or 'Up' node reference is a reference to a
> >      node in the current file and is not an external reference such as
> >      to '(dir)', then the referenced node must exist.
> > 
> > So the part at the beginning about novalidate should only be associated
> > with that point.
> 
> IMO, it would be a shame to lose the other parts of the validation (if
> this is what you are trying to say).  If eventually the decision is to
> leave some validation out of the default operation, at least please
> add some command-line option or variable to turn that back on.  Being
> able to validate the structure of a document is sometimes very
> important.

He's referring to the @novalidate command and --no-validate option
to texi2any.  Structure validation is on anyway; the question was whether
it could be turned off.  We agree that @novalidate shouldn't turn it off.



reply via email to

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