February 2010 - dev-luatex - NTG Mailing Lists

Snapshot 20070307
by Taco Hoekwater 10 May '12

10 May '12

Hi all, I decided to do a snapshot now instead of waiting for friday, because I want to start concentrating on something else besides font support issues. What's new: * Non-CID PostScript-based Opentype fonts are now combined over the entire document, and properly subsetted. The code is borrowed from xdvipdfmx with some minor adjustments Adding support for CID-keyed OpenType fonts would not be hard but at the moment I lack example input (and incentive). * A small extension to the virtual fonts structure: you can use f.fonts[1] = { 'id' = 38} to do a backreference to a previously defined font. This saves quite a few computations * There was a bug in the handling of \leaders in the output whereby it's width was taken to be twice what it should be while writing to the PDF, fixed now. * The font inclusion code is cleaned up a bit by Hartmut. * Some compilation problems were fixed. * There is (quite a bit of) debugging information printed out when OTPs are in use, because I am tracking down a bug reported by Idris. The input of each and every OTP step is shown on the terminal in a line line this: [57902][1568][58423][1568][58408][1568][58921] those are the decimal values of ocp i/o characters. If you don't need them, don't worry about it. Happy TeXing, Taco ----- Downloading and installation details: If you go to https://foundry.supelec.fr/frs/?group_id=10 you will see that there are three new released files: * luatex-snapshot-20070307.tar.bz2 This is the source tree. * luatex-snapshot-20070307-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). * luatex-snapshot-20070307-linux-i386.tar.bz2 An intel 32 linux binary (2.6.17)

3 2

(fwd) Bug#441595: not all libraries are customized, there is room for improvement
by Norbert Preining 28 Nov '10

28 Nov '10

Dear Taco, one of the lua Gurus here at Debian checked the embedded libs and found that most of the included libs are very similar to upstream, and he offered to push the few changes in your code to upstream. What do you say? (See attached email, including the diffs between current upstream of the lua libs and code in texlua). Best wishes Norbert ------------------------------------------------------------------------ Norbert Preining preining(a){jaist.ac.jp, logic.at, debian.org} JAIST, Japan TU Wien, Austria Debian TeX Task Force DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ BULDOOO a virulent red-coloured pus which generally accompanies clonmult (q.v.) and sandberge (q.v.) --- Douglas Adams, The Meaning of Liff

5 14

Cron <luatex@boekplan> /var/www/luatex.org/www/bin/luatex-svn
by root＠mail.boekplan.nl 26 Feb '10

26 Feb '10

------------------------------------------------------------------------ r3447 | taco | 2010-02-26 12:36:26 +0100 (Fri, 26 Feb 2010) | 2 lines Changed paths: M /trunk/source/texk/web2c/luatexdir/lua/lnodelib.c allow passing cal_expand_ratio and subst_ex_font to hpack ------------------------------------------------------------------------

1 0

Cron <luatex@boekplan> /var/www/luatex.org/www/bin/luatex-svn
by root＠mail.boekplan.nl 25 Feb '10

25 Feb '10

------------------------------------------------------------------------ r3445 | taco | 2010-02-25 07:47:37 +0100 (Thu, 25 Feb 2010) | 2 lines Changed paths: M /trunk/source/texk/web2c/luatexdir/lua/luainit.c put all the options in the commandline help ------------------------------------------------------------------------ r3446 | taco | 2010-02-25 07:48:31 +0100 (Thu, 25 Feb 2010) | 2 lines Changed paths: M /trunk/manual/luatexref-t.tex fix a reference ------------------------------------------------------------------------

1 0

Cron <luatex@boekplan> /var/www/luatex.org/www/bin/luatex-svn
by root＠mail.boekplan.nl 23 Feb '10

23 Feb '10

svn: OPTIONS of 'http://foundry.supelec.fr/svn/luatex': could not connect to server (http://foundry.supelec.fr)

1 0

Re: [Dev-luatex] luatex 0.60 literate progamming options
by Javier Múgica 23 Feb '10

23 Feb '10

> Flex/bison are special because they are directly supported > by Automake. Cweb is supported in the TL build system via a shell script > that handles all issues for parallel make, but still needs special build > rules -- Noweb could be handled in a similar way. > > From the build system side, I'd think normal users (i.e., people building > TL or just luaTeX) should not be required to have either Noweb or Doxygen, > as they are not required to have Autoconf, Automake, Flex, or Bison. Yes, please, no more Gnu/Linux specific stuff for we the poor guys who must work in Windows. So I like CWeb too.

1 0

Cron <luatex@boekplan> /var/www/luatex.org/www/bin/luatex-svn
by root＠mail.boekplan.nl 22 Feb '10

22 Feb '10

------------------------------------------------------------------------ r3442 | taco | 2010-02-22 08:50:17 +0100 (Mon, 22 Feb 2010) | 2 lines Changed paths: M /tools/luatextag M /trunk/build.sh M /trunk/source/texk/web2c/luatexdir/getluatexsvnversion.sh switch to the source directory before calling getluatexsvnversion.sh ------------------------------------------------------------------------ r3443 | taco | 2010-02-22 10:57:49 +0100 (Mon, 22 Feb 2010) | 2 lines Changed paths: M /trunk/manual/luatexref-t.pdf M /trunk/manual/luatexref-t.tex update command line documentation ------------------------------------------------------------------------ r3444 | taco | 2010-02-22 11:01:42 +0100 (Mon, 22 Feb 2010) | 2 lines Changed paths: M /trunk/source/texk/web2c/luatexdir/lua/luainit.c add a pointer to the reference manual in the --help output. ------------------------------------------------------------------------

1 0

svn revision ids
by Taco Hoekwater 22 Feb '10

22 Feb '10

Hi, As of revision 3436, luatex once again reports a svn revision id in the banner when it has been built on a system with a working 'svn' command. The script that fetches the number is based on an idea of Reinhard Kotucha, and uses 'svn info URL' to get the number. The script is source/texk/web2c/luatexdir/getluatexsvnrevision.sh, and it is currently run from build.sh and from the tools/luatextag script. The latter is used to create the source tarballs. I am curious how it works out for other people, as it is quite possible that I made a thinking error yet again. Best wishes, Taco

6 19

Cron <luatex@boekplan> /var/www/luatex.org/www/bin/luatex-svn
by root＠mail.boekplan.nl 21 Feb '10

21 Feb '10

------------------------------------------------------------------------ r3436 | taco | 2010-02-21 16:34:00 +0100 (Sun, 21 Feb 2010) | 4 lines Changed paths: M /tools/luatextag M /trunk/build.sh M /trunk/manual/luatexref-t.pdf M /trunk/manual/luatexref-t.tex M /trunk/source/texk/web2c/Makefile.in M /trunk/source/texk/web2c/luatexdir/am/luatex.am A /trunk/source/texk/web2c/luatexdir/getluatexsvnversion.sh M /trunk/source/texk/web2c/luatexdir/lua/lstatslib.c M /trunk/source/texk/web2c/luatexdir/lua/luainit.c M /trunk/source/texk/web2c/luatexdir/luatex.c M /trunk/source/texk/web2c/luatexdir/tex/mainbody.c M /trunk/source/texk/web2c/luatexdir/tex/mainbody.h M /trunk/source/texk/web2c/luatexdir/tex/printing.c M /trunk/source/texk/web2c/luatexdir/tex/printing.h M /trunk/source/texk/web2c/luatexdir/tex/texfileio.c Add support for revision numbers in the banner and stats library again, bump the version number to 0.51, and update the manual. Thanks to Reinhard Kotucha for the idea of getluatexsvnversion.sh. ------------------------------------------------------------------------ r3437 | oneiros | 2010-02-21 17:01:57 +0100 (Sun, 21 Feb 2010) | 2 lines Changed paths: M /trunk/source/texk/web2c/luatexdir/getluatexsvnversion.sh make it work with non-english systems ------------------------------------------------------------------------ r3438 | taco | 2010-02-21 18:00:03 +0100 (Sun, 21 Feb 2010) | 2 lines Changed paths: M /trunk/source/texk/web2c/luatexdir/getluatexsvnversion.sh new attempt at version numbers, now using svnversion ------------------------------------------------------------------------ r3439 | taco | 2010-02-21 18:04:34 +0100 (Sun, 21 Feb 2010) | 3 lines Changed paths: M /trunk/source/texk/web2c/luatexdir/getluatexsvnversion.sh 1. I forgot the `which` in front of svnversion, and 2. Have to do an svn up first. ------------------------------------------------------------------------ r3440 | taco | 2010-02-21 18:18:29 +0100 (Sun, 21 Feb 2010) | 2 lines Changed paths: M /trunk/source/texk/web2c/luatexdir/getluatexsvnversion.sh add an existence test for the .svn directory ------------------------------------------------------------------------ r3441 | oneiros | 2010-02-21 18:28:43 +0100 (Sun, 21 Feb 2010) | 2 lines Changed paths: M /trunk/source/texk/web2c/luatexdir ignore luatex_svnversion.h ------------------------------------------------------------------------

1 0

luatex 0.60 literate progamming options
by Taco Hoekwater 21 Feb '10

21 Feb '10

Hi all, Karl Berry wondered about the plans for luatex, for texlive 2010 planning. Below is the message I replied him, and in a later message he set March 31 as an initial deadline for code submissions, so that is what we have to aim for for 0.60. The most important immediate decision is what to do about the literate programming issue, as we explicitly promised that for the 0.60 release. Here is the list of serious candidates (in my current opinion): * Cweb http://www-cs-faculty.stanford.edu/~knuth/cweb.html * Doxygen http://www.stack.nl/~dimitri/doxygen/ * Noweb http://www.cs.tufts.edu/~nr/noweb/ Cweb has a head start because of its relation to WEB (we all like DEK, the needed tools are in texlive, the retained comments already use the correct formatting, and perhaps most importantly Hartmut and I are used to its quirks). But that does not mean it should automatically be the tool to use. Doxygen has a number of advantages: it formalizes api documentation, it supports html output as well as latex, its use is much more common, and the input keeps looking like normal C files to the build tools (important for dependency tracking in make). Finally, noweb is interesting because it is much simpler than cweb and also (mainly) because Norman Ramsey is/was planning to redo it in lua, which would mean that in the end it might be possible to use luatex to generate itself and its documentation. But it has most of the same build-time drawbacks that cweb has. I'll be studying these options for the next week or so, and I hope you will do the same. Also, let me know if there are other candidates that are worth investigating. Best wishes, Taco PS besides the core luatex team, I put dev-luatex and a bunch of people in the CC list that may have interesting input to the discussion. Taco Hoekwater wrote: > Karl Berry wrote: >> >> That leaves LuaTeX. Taco, what should we aim for shipping in 2010, and >> when? (And let's be sure that we update context and luatex in TL at the >> same time this year, so context mkiv stands a chance.) > > > For luatex itself, the two major plans for 0.60 are > 1. go back to Cweb (or something similar) from plain C > 2. consolidate binary lua module loading > unfortunately, it is likely both will affect the build process > > Point 1 still needs a decision to be made (use cweb, use doxygen, or > write something ourselves), I expect that decision to be made in this > month, and the initial implementation to follow a few weeks later. > > Point 2 has unsolved issues with the use of the lua core, which > really should become a dynamic, private dll to avoid problems between > the lua core symbols use by such external modules and luatex's > embedded (patched) lua core symbols. I am not too thrilled about > implementing this, so I have postponed it until now. (a longer, more > technical email about this will follow in a few days) > > There are some other things planned for luatex 0.60, but those > are relatively minor and, most importantly, wont affect the build > process much. So once the two point above are resolved, the code > could go into the TL repository. Sounds like end of March would > be doable for that. > > Meanwhile, don't forget metapost, massive amounts of work going on > there. But metapost 2 will not be finished before early summer (at > the very earliest), so I guess the best solution is to stick with > metapost 1.2 in TL 2010, and possibly also include a pre-release of > metapost 2, if anything release-able is ready in time. > > I think actually it would help if you set straight deadlines > for code submissions, that way I can reschedule the development > work to match those. Both metapost and luatex are actively > developed: there is a never a point where there are no great > changes planned. > > Best wishes, > Taco

5 6