On Fri, Mar 11, 2022 at 02:09:35AM +0100, Patrice Dumas wrote:
> On Sun, Feb 20, 2022 at 10:42:25AM +, Gavin Smith wrote:
> >
> > Again I think the name of the option shouldn't contain the work "book",
> > as it is too vague.
>
> I added a customization variable named 'NO_TOP_NODE_OUTPUT' whi
Patrice Dumas wrote:
On Sun, Feb 20, 2022 at 10:42:25AM +, Gavin Smith wrote:
Again I think the name of the option shouldn't contain the work "book",
as it is too vague.
I added a customization variable named 'NO_TOP_NODE_OUTPUT' which, if
set is the book-like output. There is no
On Sun, Feb 20, 2022 at 10:42:25AM +, Gavin Smith wrote:
>
> Again I think the name of the option shouldn't contain the work "book",
> as it is too vague.
I added a customization variable named 'NO_TOP_NODE_OUTPUT' which, if
set is the book-like output. There is no reference to a book like
s
On Fri, Mar 04, 2022 at 06:23:50PM +, Gavin Smith wrote:
> My preference would be to keep Makefile.am a purely UTF-8 or even
> ASCII file. (This would avoid us having to contend with encoding
> issues in Automake as well as in Texinfo.)
There are utf8 file names in Makefile.am.
> If we reall
On Wed, Mar 09, 2022 at 07:44:29PM -0800, Mike Swanson wrote:
> I suspect it should be possible to catch this error from the Perl
> script and at least provide a warning that it was unable to create the
> non-UTF8 file name.
I made some change such that a test is skipped if it requires recoded
fil
On Wed, Mar 09, 2022 at 07:44:29PM -0800, Mike Swanson wrote:
> On Thu, 2022-03-10 at 04:35 +0100, Patrice Dumas wrote:
> > Now it is generated just before the tests in tp/tests. But won't the
> > issue be there too not at checkout time, but at make check time?
> > Could
> > you please test it?
>
