bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

texi2dvi changes


From: Vincent Belaïche
Subject: texi2dvi changes
Date: Thu, 24 Sep 2015 22:54:00 +0200

Hello Gavin,

Le 22/09/2015 19:53, Gavin Smith a écrit :
> Hello Vincent and everyone else,
>
> Information about the changes to texi2dvi that I've made:
>
> No longer use a trick of renaming the recorder file to *.flz. In fact,
> no special tricks at all in texi2dvi to handle this case. So the
> recorder file will have the fls suffix, which Vincent pointed out was
> what would be expected.
>

Great, let us not make unusual things...

> The current working directory is back at the beginning of TEXINPUTS.
>

Great too. Once again, even if this was a MikTeX bug (FYI:
https://sourceforge.net/p/miktex/bugs/2401/), I think that giving cur
dir less precedence was too unusual.

> If someone uses an "fl" index with the recorder, I expect either the
> index to be blank, or to be the recorder file interpreted as TeX
> source (a great ugly mess). I've had both happen for different test
> files, although am not sure what made the difference. It might work
> anyway, by the same fluke that got it to work with MikTeX before.
>
> With a change I prepared to texinfo.tex, fl indices also worked with
> the recorder as well as the log file. This change changed the file
> extensions that are used for such an index.
>

Ok, this is the simpler correction. Maybe we could have additionnally
some warning made by texi2dvi if an fl index is detected and the texinfo
version is too old.

> I pointed out that the log files were being grep'd a lot to get the
> list of generated files. This won't happen as much now.
>

I have seen that what you have done goes far beyond reverting the
TEXINPUTS order to what it was originally and removing the
.flz. Well... maybe it would have been more careful to sort out what we
already have on the table, rather than open another item with reducing
the amount of log grepping. Anyway, on the other hand that was a good
occasion to do it, as everybody has now warmed up on this texi2dvi.

As a preliminary comment I would say that all the xxx_p named function
have now misleading names as the `_p' suffix stands for `predicate', ie
involves that the function returns a boolean condition to be used in a
boolean expression (like within an `if ... ;'. Now these functions do
some border effect (ie `echo ...'), so the names should be changed (ie
dropping the `_p' tail) accordingly.

> This was a big change to a complex script with many ways of running
> it, so it's quite possible that something's broken. (I've deliberately
> refrained from uploading texi2dvi to the FTP site for the last few
> revisions for that reason.)
>
> Can anybody try the script with LaTeX source with BibTeX, or else send
> me a test case? I want to make sure the BibTeX files are checked
> properly.

I have done that. See attached test file and the session (essai.session)
where I try a compilation both in --tidy mode, and then w/o --tidy for
an essai.tex file using a bib. I also made a trial on a Texinfo file.



>
> Gavin

I seems that everything is OK, at least with this test. Congratulation,
good job!

VBR,
        Vincent




---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
http://www.avast.com

Attachment: essai.tgz
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]