Re: Fwd: REVIEW REQUEST - user manual generation

[Vincent Belaïche]

Hello Gavin,

Answers below

Le 28/04/2016 20:35, Gavin Smith a écrit :
> On 28 April 2016 at 09:30, Vincent Belaïche <address@hidden> wrote:

[...]

>
> That's what texi2dvi does. The foo~bar.texi file has a line in it
> "\input texinfo" which loads texinfo.tex, and the catcode and active
> definition of ~ are changed again. So the catcode given on the
> command-line isn't lasting.

Yes, the changed catcode for ~ isn't lasting if you compile a Texinfo
file --- which texi2dvi is primary made for --- but it _is_ lasting when
texi2dvi is used to compile a LaTeX file (something I had noticed with
another problem report a few months ago). This is why I was writing that
the method which I proposed (in essence make the catcoding group local,
and then expand it after-group) is superior: it does not affect the
catcodes outside the command line even with LaTeX (well, I have not
tested it yet).

Anyway, this is not the problem on the table now, we are talking
primarilly about another special character: space.

VBR,
        Vincent.