bug-texinfo
[Top][All Lists]
Advanced

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

Re: [bug #43122] texi2dvi does not compile enough times to get toc


From: Vincent Belaïche
Subject: Re: [bug #43122] texi2dvi does not compile enough times to get toc
Date: Wed, 16 Sep 2015 08:28:12 +0200


Le 16/09/2015 00:25, Gavin Smith a écrit :

[...]

>
> Because the *.fls (sorted fl index file) is clobbered by the *.fls
> recorder file, so it is no more. I had to change the order to get this
> to work, so that the *.fls (sorted fl index file) will be created
> again, after the recorder file has been renamed.

Since the nearly beginning of this whole tale of woe, I am thinking that
it would be better to solve the .fls case in texinfo.tex also rather
than just texi2dvi, my first idea was some fl<->_0 translation, and my
final idea is that non sorted index I should be named .I.idx, and sorted
index I should be named .I.ind.

- This would follow the rule that filename extensions are used with
  parcimony and give some indication on the file format, and

- This would make Texinfo closer to LaTeX to that respect.

- This would not break the support of other languages (e.g. latex) in
  addition to Texinfo --- well I don't know if this support really is
  used by anybody, but if not it just makes the code more complex.

Then tex2dvi would just deal the compatibility/tool interoperability
issues:

- if the index filename does not match \.[^.]+\.idx\', then index would
  be handled in the traditional way with an error message in the case
  that
  - the index name is fl
  - recorder is used instead of \openout
  and with a warning message "update your texinfo.tex" otherwise.
  The error message would also tell how to solve the error
  - udpate texinfo.tex (preferred solution)
  - rename index to something else than fl
  - try and use \openout (if TeX engines allows it)

- otherwise, the sorted index would just be renamed from .idxs to .ind
  in case that texindex is too old to do it alone, and there would be a
  warning message "update your texindex tool"


The above would be the ideal (meaning less risky, more futureproof) fix
in my opinion, but I can understand that there is so much tool
interoperability issues that one is hesitant to go this way.


VBR,
        Vincent





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




reply via email to

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