/usr/share/doc/liblatex-driver-perl/TODO is in liblatex-driver-perl 0.12-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 | #================================================== -*- indented-text -*-
#
# TODO
#
# DESCRIPTION
# TODO list for the LaTeX-Driver package, containing known bugs,
# limitations, planned enhancements, long term visions and a few
# whacky ideas.
#
# AUTHOR
# Andrew Ford <a.ford@ford-mason.co.uk>
#
#------------------------------------------------------------------------
# $Id: TODO 84 2012-08-30 20:19:25Z andrew $
#========================================================================
#------------------------------------------------------------------------
# Miscellaneous
#------------------------------------------------------------------------
* add handling of luatex
* improve Kwalitee and general adherance to Perl best practice [MOSTLY DONE]
* add a script to invoke LaTeX::Driver on a specified file - need to
think of a good name and a sensible set of options
* add checks for timestamps (a la "make" and "latexmk")
* check the mechanism whereby latex (or pdflatex) is re-run if the
document contains undefined references after the first run. Bibtex
is re-run if undefined citations are reported by latex, and
makeindex is run if the driver detects a ".idx" file. If bibtex or
makeindex are run then latex (or pdflatex) are run up to three more
times to allow forward references to stabilize.
This should all be coped with now but need to check on edge cases
* look at how path variables could be specified to the filter
(TEXINPUTS, TEXINPUTS_latex, TEXINPUTS_pdflatex, BIBINPUTS, etc),
and how these should interact with the system paths.
* get the filter working on Win32
how does one set environment variables with command.exe?
* write unit tests for error conditions (invalid .bib file, etc)
* test the scripts
* make test scripts check for presence of tex components, such as
dvitype, lastpage.sty
* provide a facility for specifying pre- and post-processors,
e.g. gnuplot, metapost, tpic or other graphics processors. May need
to copy data files from the source location to the temporary
directory.
* benchmark the filter
Note that the latex filter runs up to eight external programs, so it
isn't very fast. But for modest documents the performance is
adequate, even for interactive applications.
* expand the documentation
* try to fix the line numbers when formatting a template document with
latex2xxx results in latex errors. If we get errors with line
numbers, they will relate to the expanded document - not to the
template source lines, but we could find the mapping by reexpanding
the template, adding line numbers in TT2 "#" comments to the
template source, and then go to the line number in error and read
off the original line number.
* check for further conditions that require re-running of one or more
LaTeX programs.
|