On 5/19/2015 11:43 PM, Wybo Dekker wrote:
Ah - right, in version 0.80 they are logged. However: in a different format:
pdftex: \openout3 = `myfile.txt'. luatex: \openout3 = myfile.txt
As a result, texi2dvi still doesn't work. Of course, such scripts can easily be adapted, but I think that should not be necessary.
Indeed it should not be that hard to adapt the script that uses that info. Also, future luatex versions might have a bit different logging once we start upgrading that bit (and these l/r quotes look funny anyway as any other language wrould use 'xx' or "xx".)
Isn't it more robust to let text2dvi (whatever it does) let write some explicit and easy to recognize message to the log? For instance the number 3 in the message can be any valid write related number esp if we decide to upgrade the write/read mechanisms.
On 2015-05-19 14:52, Hans Hagen wrote:
On 5/19/2015 2:17 PM, Wybo Dekker wrote:
Compiling this source:
with pdftex generates a log file containing:
\openout3 = `myfile.txt'.
Compilation with luatex does not. Compare the attached log files.
Some scripts (like latexmk and texi2dvi) depend on such log entries for the detection of auxiliary files and they therefore don't co-operate properly with lua(la)tex.
can you check with version 0.80
Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl
dev-luatex mailing list firstname.lastname@example.org http://www.ntg.nl/mailman/listinfo/dev-luatex