Failure in html output - Reference to nonexistent nodes
Some time ago I discussed the problem that calling a reference to a nonexistent node when generating .info files. When outputting html, reference to nonexistent node also gives a problem. @ref reference to nonexistent node `igc03--Sicl--CircAmRg' Problem is aggravated because the failure stops the generation of any files. When using texi2pdf, one gets in the output pdf document [igc03–Sicl–CircAmRg], page , This is much better than not generating any output. I have read some innovative ideas from Language Designer Luca Saiu, to make programs run even with errors. These ideas will certainly be interesting, because as with the pdf output, the difficulties are transplanted in the output. Then one can eventually go and fix them. However, the problem with undefined ref will not stop the author from continuing with his work until he resolves undefined ref. I mention this also for the generation of .info files.
Re: Failure in html output - Reference to nonexistent nodes
On Sat, Nov 14, 2020 at 03:13:27PM +0100, Christopher Dimech wrote: > Some time ago I discussed the problem that calling a reference > to a nonexistent node when generating .info files. > > When outputting html, reference to nonexistent node also gives a > problem. > > @ref reference to nonexistent node `igc03--Sicl--CircAmRg' That seems to be a good thing to me, this is an clearly an error. > Problem is aggravated because the failure stops the > generation of any files. > > When using texi2pdf, one gets in the output pdf document > > [igc03–Sicl–CircAmRg], page , > > This is much better than not generating any output. My wild guess is that opinions are probably divided on that matter. But there is a possibility with texi2any to generate input even in case of errors, with the option --force. The option --error-limit may also be of use in that context. There is also --no-warn that an be used to silence the warnings. -- Pat
Re: Failure in html output - Reference to nonexistent nodes
Still for productivity's sake, output is better than no output. This is especially important for large works, where the author does not want complete failure because of some inconsistency. I am suggesting that the error message still shows up in the output. I suggest a variable that can be used for strict checking. > Sent: Saturday, November 14, 2020 at 4:09 PM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" , "Gavin Smith" > > Subject: Re: Failure in html output - Reference to nonexistent nodes > > On Sat, Nov 14, 2020 at 03:13:27PM +0100, Christopher Dimech wrote: > > Some time ago I discussed the problem that calling a reference > > to a nonexistent node when generating .info files. > > > > When outputting html, reference to nonexistent node also gives a > > problem. > > > > @ref reference to nonexistent node `igc03--Sicl--CircAmRg' > > That seems to be a good thing to me, this is an clearly an error. > > > Problem is aggravated because the failure stops the > > generation of any files. > > > > When using texi2pdf, one gets in the output pdf document > > > > [igc03–Sicl–CircAmRg], page , > > > > This is much better than not generating any output. > > My wild guess is that opinions are probably divided on that matter. > > But there is a possibility with texi2any to generate input even in case > of errors, with the option --force. The option --error-limit may also be > of use in that context. There is also --no-warn that an be used to > silence the warnings. > > -- > Pat >
Re: Failure in html output - Reference to nonexistent nodes
On Sat, Nov 14, 2020 at 04:09:14PM +0100, Patrice Dumas wrote: > On Sat, Nov 14, 2020 at 03:13:27PM +0100, Christopher Dimech wrote: > > Some time ago I discussed the problem that calling a reference > > to a nonexistent node when generating .info files. > > > > When outputting html, reference to nonexistent node also gives a > > problem. > > > > @ref reference to nonexistent node `igc03--Sicl--CircAmRg' > > That seems to be a good thing to me, this is an clearly an error. > > > Problem is aggravated because the failure stops the > > generation of any files. > > > > When using texi2pdf, one gets in the output pdf document > > > > [igc03–Sicl–CircAmRg], page , > > > > This is much better than not generating any output. > > My wild guess is that opinions are probably divided on that matter. > > But there is a possibility with texi2any to generate input even in case > of errors, with the option --force. The option --error-limit may also be > of use in that context. There is also --no-warn that an be used to > silence the warnings. Another possibility is to put @novalidate in the document.
Re: Failure in html output - Reference to nonexistent nodes
> Another possibility is to put @novalidate in the document. The above is good, but we still want the error to show and in the output to say unidentified, or something of the sort. Howe > Sent: Saturday, November 14, 2020 at 6:28 PM > From: "Gavin Smith" > To: "Patrice Dumas" , "Christopher Dimech" > , "help-texinfo gnu" > Subject: Re: Failure in html output - Reference to nonexistent nodes > > On Sat, Nov 14, 2020 at 04:09:14PM +0100, Patrice Dumas wrote: > > On Sat, Nov 14, 2020 at 03:13:27PM +0100, Christopher Dimech wrote: > > > Some time ago I discussed the problem that calling a reference > > > to a nonexistent node when generating .info files. > > > > > > When outputting html, reference to nonexistent node also gives a > > > problem. > > > > > > @ref reference to nonexistent node `igc03--Sicl--CircAmRg' > > > > That seems to be a good thing to me, this is an clearly an error. > > > > > Problem is aggravated because the failure stops the > > > generation of any files. > > > > > > When using texi2pdf, one gets in the output pdf document > > > > > > [igc03–Sicl–CircAmRg], page , > > > > > > This is much better than not generating any output. > > > > My wild guess is that opinions are probably divided on that matter. > > > > But there is a possibility with texi2any to generate input even in case > > of errors, with the option --force. The option --error-limit may also be > > of use in that context. There is also --no-warn that an be used to > > silence the warnings. > > Another possibility is to put @novalidate in the document. >
Re: Failure in html output - Reference to nonexistent nodes
On Sat, Nov 14, 2020 at 06:26:07PM +0100, Christopher Dimech wrote: > Still for productivity's sake, output is better than no output. > This is especially important for large works, where the author > does not want complete failure because of some inconsistency. It really depends. In particular for automatic generation, in Makefile, no document, I think, is better than a document if it failed. When calling manually texi2any, it seems to me that it is better if there is systematically an output. > I suggest a variable that can be used for strict checking. I do not understand that one. In general texi2any does strict checking, and the output can be silenced with --no-warn. -- Pat
