Hi all, Almost a month after the previous snapshot, I have a released a new one. The current snapshot is much more of a work-in-progress than the previous one, so you can expect glitches and changes to the offered new functionality. Also , I have not gotten round to looking at Javier's problem with \lua inside OTPs yet, and there is at least one known problem with the current snapshot: the "output written to " message sometimes contains utter nonsense. That said, this snapshot also fixes a big bug in the previous version, as well as a few smaller ones. Noteworthy are: * the calculations that converted lua strings into tex units were horrendously wrong, this was discovered by Pawel. * io.lines() was still using the old, line ending sensitive, code from the lua core distribution --------------- Most of the really new stuff is internal in nature, with only a few bits user-visible. The big change is that all of the font manupulation that is done by 'TeX proper' (the Knuthian bits) is now isolated behind an internal API, with the implementation (partially re) written in C. This opens the road to a more extensible font machinery, but not much of that is implemented at present yet. What has been done: * The main font memory is allocated as needed^(1) instead of statically pre-allocated. * ligatures and kerns are separated completely from each other, so use of \noligatures no longer inhibits kerning as well * Metrics can be loaded using a callback: 'define_font'. The value returned should be a lua table representing a tfm file. * there is a new lua table: font. It has one function: font.read_tfm() that returns a table reprentation of the tfm contents, for use with the above mentioned callback (1) Currently, there is still a upper limit of 5500 fonts, because font identifiers like \tenrm need to point somewhere in the equivalence table. This limitation will be removed soon. Most likely things to be buggy or just wrong in this snapshot: * the interaction between automatically inserted hyphenation and ligatures (the function reconstitute(), for insiders) * ligatures with word boundaries. * I dropped suppport for "Level 1" OFM files. I would like to have a try at those extended font files, but I lack examples (fonts nor documents). I am not even sure such fonts have ever existed in the 'real world'. -------------- My focus for the following week(s) will be on the non-Knuth parts of the font machinery (virtual fonts, mapfiles, pdf output of wide fonts). -------------- An unrelated change is the inclusion of version 0.2 of the Lua "lpeg" library for string matching. See http://www.inf.puc-rio.br/~roberto/lpeg.html for full details on usage. --------------- And I've updated the manual, as always (pdf is inside the bz2 file) Have fun, 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-20070105.tar.bz2 This is the source tree. * luatex-snapshot-20070105-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).
Taco Hoekwater wrote:
Taco Hoekwater wrote:
--------------
My focus for the following week(s) will be on the non-Knuth parts of the font machinery (virtual fonts, mapfiles, pdf output of wide fonts).
I forgot: and merging the pdftex 1.40.0 release of course.
ah, small detail -) 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 -----------------------------------------------------------------
On Fre, 05 Jan 2007, Taco Hoekwater wrote:
* I dropped suppport for "Level 1" OFM files. I would like to have a try at those extended font files, but I lack examples (fonts nor documents). I am not even sure such fonts have ever existed in the 'real world'.
Oh I played around with them, but even the tools for generating the ofm
level 1 fonts didn't work. It was a pain ...
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining
On Fre, 05 Jan 2007, Arthur Reutenauer wrote:
Oh I played around with them, but even the tools for generating the ofm level 1 fonts didn't work. It was a pain ...
I wrote a patch for it years ago, but it never made it to the sources...
AHHHHH hmm, what a pity... I wanted to use ofmv1 fonts for my tibetan
support stuff. Well, I did it differently. Now it is too late. luatex
will go a better way, or Omega_2 if it ever appears ;-)
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining
Arthur Reutenauer wrote:
Oh I played around with them, but even the tools for generating the ofm level 1 fonts didn't work. It was a pain ...
I wrote a patch for it years ago, but it never made it to the sources...
To add to the general confusion, regular (level 0) ofm files report (OFMLEVEL D 1) at the top of ofm2opl's output, as I discovered this when I finally (!) found a working version of ofm2opl. That had me worried quite a bit, but luckily this seems to be a fluke of ofm2opl. Cheers, Taco
To add to the general confusion, regular (level 0) ofm files report
(OFMLEVEL D 1)
at the top of ofm2opl's output,
Yes, that was it, and if you corrected it and ran opl2ofm on the corrected output, it choked because it believed it was reading an ofm level 65535 (or so); in the sources it was obvious there was a spurious ±1 at some stage... but interestingly enough, the whole ofm2opl / opl2ofm / etc. bundle was coherent with its own output (but not with the original input). If you're using Debian, I believe the binary is patched thanks to a bug-report by my friend Joël Riou :-)
On Fri, Jan 05, 2007 at 06:41:27PM +0100, Arthur Reutenauer wrote:
Oh I played around with them, but even the tools for generating the ofm level 1 fonts didn't work. It was a pain ...
I wrote a patch for it years ago, but it never made it to the sources...
Just for the completeness of this thread, it's here: http://www.ntg.nl/pipermail/aleph/2005-July/000409.html Of course, in order to use it, you have to download the source files (http://omega.enstb.org/distrib/omega-1.23.4.tar.bz2), patch them, compile everything from scratch and then install (at least) the fonts tools; the other programs related to omega, including omega proper, aren't affected by this patch.
On Fre, 05 Jan 2007, Taco Hoekwater wrote:
Almost a month after the previous snapshot, I have a released a new one. The current snapshot is much more of a work-in-progress
Debian users can install the new luatex snapshot as usual:
deb(-src) http://www.tug.org/texlive/Debian/ luatex/
to be added to /etc/apt/sources.list and
aptitude update
aptitude install luatex-snapshot
The source file and the Release file is signed with my debian key.
Thanks Taco and the whole team!
@Taco: If you prefer that I put the debs somewhere else (in addition)
let me know.
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining
participants (4)
-
Arthur Reutenauer
-
Hans Hagen
-
Norbert Preining
-
Taco Hoekwater