Re: Fwd: REVIEW REQUEST - user manual generation

These two things also work: --8<8<8<8<8<-- begin -->8>8>8>8>8 in_input_funnies=`echo "$in_input" \ | $SED -e 's![^}#$%&^_{~]!!g; s!\(.\)!\1\'" "'!g' \ | uniq` --8<8<8<8<8<-- end -->8>8>8>8>8

Re: Fwd: REVIEW REQUEST - user manual generation

Answering to myself... >Hello, > >Le 03/06/2016 à 18:15, Gavin Smith a écrit : >>> The problem is that my MSYS sed was version 3.02, and it did not >>> recognise \n in the replacement string when you want to make each funny >>> character on one line. I made some test with my git bash --- which

Re: Fwd: REVIEW REQUEST - user manual generation

Hello Gavin, Le 01/06/2016 à 22:40, Gavin Smith a écrit : > On 10 May 2016 at 10:13, Vincent Belaïche wrote: >> Hello Gavin, >> >> Answering to myself: I had been a bit too hasty, patch #7 sent >> preivously was working properly, but the naming of variable >>

Re: Fwd: REVIEW REQUEST - user manual generation

On 10 May 2016 at 10:13, Vincent Belaïche wrote: > Hello Gavin, > > Answering to myself: I had been a bit too hasty, patch #7 sent > preivously was working properly, but the naming of variable > _run_tex_in_input_funnies was not corresponding any longer to its >

Re: Fwd: REVIEW REQUEST - user manual generation

On 9 May 2016 at 20:21, Gavin Smith wrote: >> I guess that with all those changes, but except for the space that is a >> deep tex engine limitation, only the Devil could find a valid filename >> not working. >> >>Vincent. >> I was going to say, I don't think it's

Re: Fwd: REVIEW REQUEST - user manual generation

On 9 May 2016 at 14:03, Vincent Belaïche wrote: > Hello Gavin, >> >> Latest version at >> >> http://svn.savannah.gnu.org/viewvc/trunk/util/texi2dvi?revision=7147=texinfo=markup > > Ok, > > I have done the following modifications: > > 1) use sed instead of grep to test

Re: Fwd: REVIEW REQUEST - user manual generation

Indeed, I don't believe there is any perfect way to support filenames with spaces. Double-quoted "foo bar.tex" is the most likely. I don't know if that works in miktex. Multiple consecutive spaces is even harder, e.g., see thread starting at

Re: Fwd: REVIEW REQUEST - user manual generation

Answering to myself below... >Feedback below... > >Le 04/05/2016 22:57, Gavin Smith a écrit : >> On 2 May 2016 at 20:53, Gavin Smith wrote: >>> On 29 April 2016 at 09:27, Vincent Belaïche >>> wrote: Attached is an attempt to do that.

Re: Fwd: REVIEW REQUEST - user manual generation

Feedback below... Le 04/05/2016 22:57, Gavin Smith a écrit : > On 2 May 2016 at 20:53, Gavin Smith wrote: >> On 29 April 2016 at 09:27, Vincent Belaïche >> wrote: >>> Attached is an attempt to do that. Unfortunately using \egroup for group

Re: Fwd: REVIEW REQUEST - user manual generation

Answering to myself, Le 03/05/2016 11:13, Vincent Belaïche a écrit : > > > Hello, > > Answers below, > [...] > > I suggest we go to this kind of solution for robustifying texi2dvi > w.r.t. to stange filenames. I want to refine it further in order to: > > - remove current handling of ~ and make

Re: Fwd: REVIEW REQUEST - user manual generation

On 2 May 2016 at 20:53, Gavin Smith wrote: > I've been working on a patch to avoid the use of absolute paths > altogether, but it isn't done yet. Here's what I have so far. It needs more testing and scrutiny, though. Index: ChangeLog

Re: Fwd: REVIEW REQUEST - user manual generation

Hello, Answers below, Le 02/05/2016 21:53, Gavin Smith a écrit : > On 29 April 2016 at 09:27, Vincent Belaïche > wrote: >> Attached is an attempt to do that. Unfortunately using \egroup for group >> end does not work, because whether it is a \toks or a \def you

Re: Fwd: REVIEW REQUEST - user manual generation

On 29 April 2016 at 09:27, Vincent Belaïche wrote: > Attached is an attempt to do that. Unfortunately using \egroup for group > end does not work, because whether it is a \toks or a \def you need the > the end of the definition terminated by a catcode=2 character. > >

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

Re: Fwd: REVIEW REQUEST - user manual generation

<>| are not valid in filenames They are on Unix. -k

Fwd: Fwd: REVIEW REQUEST - user manual generation

On 27 April 2016 at 22:33, Vincent Belaïche wrote: >> The solution is presumably to avoid using an absolute path. > > The space in filename problem is not sh lack of quoting. This is a TeX > limitation of \input. \input gets the filname up to the first space or >

Re: Fwd: REVIEW REQUEST - user manual generation

On 28 April 2016 at 09:30, Vincent Belaïche wrote: > - catcoding to letters all the tex special characters that are valid in > filename, that is to say: {}$#~ and space. I am using < > and | in > place of { } and space respectively as <>| are not valid in filenames

Re: Fwd: REVIEW REQUEST - user manual generation

One more patch --- see comments below Le 28/04/2016 00:32, Stephen H. Dawson a écrit : > Nice. Glad to see people working together. It is a rarity in life I > greatly enjoy experiencing. :-) > > Thank You, > Stephen H. Dawson > (865) 804-3454 > http://www.linkedin.com/in/shdcs > > > On