Re: texi2dvi unexpected behaivoir

On 29 April 2016 at 11:48, wrote: > I traced the script until the following point: > texi2dvi line 991 in function 'filter_files': > test -n "$xref_files_new" && echo "$xref_files_new" | > It seems that the script traps at this point and calls the function >

texi2dvi unexpected behaivoir

Dear developers, when compiling tex documents using texi2pdf, texi2pdf returns 1, although a pdf-file is generated after exactly one compilation cycle. Within the document the references are missing. A minimal example to reproduce the behaviour is this file: foo.tex --- \documentclass{article}

Re: Fwd: REVIEW REQUEST - user manual generation

Le 29/04/2016 00:42, Karl Berry a écrit : > <>| are not valid in filenames > > They are on Unix. -k Ooops... After some search on the Web I found this interesting discussion: http://stackoverflow.com/questions/1976007/what-characters-are-forbidden-in-windows-and-linux-directory-names In

Re: Fwd: REVIEW REQUEST - user manual generation

Le 29/04/2016 08:55, Vincent Belaïche a écrit : > > > Le 29/04/2016 00:42, Karl Berry a écrit : >> <>| are not valid in filenames >> >> They are on Unix. -k > > [...] > > However, instead of <>| I could use > > \bgroup for group beginning > \egroup for group end > nul for space. >

Re: Fwd: REVIEW REQUEST - user manual generation

Hello Gavin, Answers below Le 28/04/2016 20:35, Gavin Smith a écrit : > On 28 April 2016 at 09:30, Vincent Belaïche > 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