Hi all, I have just released snapshot 20070119. The largest new bit is the existence of a font.fonts array, that you can use to query/adjust the internal defined tex fonts. See the manual for more details. Two small new lua extensions are added as well: * os.setenv() -- to change the environment * os.exec() -- a non-returning os.execute() And a bit of cleanup in the commandline processing. Also patched is the problem with building in MacOSX that Arthur reported, and some updates to the manual. Best, Taco ----- Downloading and installation details: If you go to https://foundry.supelec.fr/frs/?group_id=10 you will see that there are two new released files: * luatex-snapshot-20070119.tar.bz2 This is the source tree. * luatex-snapshot-20070119-win32.zip A cross-compiled (mingw) windows binary. This is a web2c based binary, so it needs a texmf.cnf file (It will NOT work if you have only miktex installed).
Hi all! On Fre, 19 Jan 2007, Taco Hoekwater wrote:
I have just released snapshot 20070119.
deb http://www.tug.org/texlive/Debian/ luatex/
deb-src http://www.tug.org/texlive/Debian/ luatex/
As usual.
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining
And a bit of cleanup in the commandline processing.
I assume it's the reason why luatex has a weird behaviour when running in ini mode: # $ ./luatex -ini # kpathsea mode needs a --progname or --fmt switch It works, indeed, when given a --progname switch (with argument luatex, for instance), and it can output format files. Afterwards, calling luatex works because it's not in ini mode anymore, and provided it can find the format file. Maybe it's really the intent that ini be used only along with progname or fmt, but until recently it was not the case (since up to rev. 252 I could use this very simple script to output format files: "./luatex -jobname=luatex -ini '\input plain\dump'").
Also patched is the problem with building in MacOSX that Arthur reported,
Indeed, it works all right as far as compilation is concerned. Arthur
Arthur Reutenauer wrote:
And a bit of cleanup in the commandline processing.
I assume it's the reason why luatex has a weird behaviour when running in ini mode:
# $ ./luatex -ini # kpathsea mode needs a --progname or --fmt switch
The error handler was in fact already there, but only activated by --lua mode. The idea was to let the lua init script do the commandline processing in that case. In the 'traditional' mode, the commandline was handled like in traditional tex. In the cleanup, the code is more of a hybrid, trying to be as compatible with old TeX as possible while still allowing all of the new options. The error goes away if you specify a filename, although it is not completely the same. This command still works: $ ./luatex -ini plain.ini and it sets progname to 'plain'. In contrast, this old commandline: $ ./luatex -ini '\input plain \dump' would set progname to 'luatex' I could remove the restriction, but I was hoping to get away from the first-line-starts-on-the-commandline, because it is not like any other program I know of. Other opinions are welcome. Best, Taco
Taco Hoekwater wrote:
Arthur Reutenauer wrote:
And a bit of cleanup in the commandline processing.
I assume it's the reason why luatex has a weird behaviour when running in ini mode:
# $ ./luatex -ini # kpathsea mode needs a --progname or --fmt switch
The error handler was in fact already there, but only activated by --lua mode. The idea was to let the lua init script do the commandline processing in that case. In the 'traditional' mode, the commandline was handled like in traditional tex.
In the cleanup, the code is more of a hybrid, trying to be as compatible with old TeX as possible while still allowing all of the new options. The error goes away if you specify a filename, although it is not completely the same.
This command still works:
$ ./luatex -ini plain.ini
and it sets progname to 'plain'.
In contrast, this old commandline:
$ ./luatex -ini '\input plain \dump'
would set progname to 'luatex'
I could remove the restriction, but I was hoping to get away from the first-line-starts-on-the-commandline, because it is not like any other program I know of.
indeed it makes sense to get rid of that first line thing Hans -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (4)
-
Arthur Reutenauer -
Hans Hagen -
Norbert Preining -
Taco Hoekwater