- dev-luatex - NTG Mailing Lists

Fwd: CTAN Update: ant
by Martin Schröder 18 Dec '07

18 Dec '07

It's alive :-) ---------- Forwarded message ---------- From: CTAN Announcements <ctan-ann(a)dante.de> Date: 18.12.2007 10:13 Subject: CTAN Update: ant To: ctan-ann(a)dante.de On Tue, 18 Dec 2007, Achim Blumensath submitted an update to the ant package. Location on CTAN: /systems/ant Summary description: ant is not TeX License type: pd Announcement text: ---------------------------------------------------------------------- I'm pleased to announce the release of ant version 0.8. The archive can be found at http://ant.berlios.de ant is a typesetting system inspired by TeX. It does not aim at complete compatibility with TeX but focuses instead on a flexible, clean, and modular design. ant is public domain. New in this release are: o support for margin kerning o many improvements of the built in scripting language o various bug fixes and minor improvements ---------------------------------------------------------------------- This package is located at http://mirror.ctan.org/systems/ant . More information is at http://tug.ctan.org/info/?id=ant (if the package is new it may take a day for that information to appear). We are supported by the TeX Users Group http://www.tug.org . Please join a users group; see http://www.tug.org/usergroups.html . _______________________________________________ Thanks for the upload. For the CTAN Team Rainer Schöpf

3 3

beta 0.20.2 released
by Taco Hoekwater 17 Dec '07

17 Dec '07

Hi all, I have just uploaded the archives for luatex 0.20.2. This is a simple bugfix release for last week's beta: * some portability fixes to the build scripts * a fix for multi-\span in alignments causing unbreakable loops * manual improvements from Jonathan Sauer * fix for undefined csnames in \directlua if web2c's hash_extra is nonzero * fix for LR text inside of a RL document * fix for open_read_file callback not being called unless find_read_file was also registered * removed the ocp status message when \ocps are not actually used * "unicodeenc" in the fontforge to_table renamed to "unicode" for improved consistency I have uploaded source and linux/win32 binaries to http://foundry.supelec.fr/projects/luatex/ Have fun, Taco

1 0

.BEILMOPS or how I stopped worrying and love Open Source
by Jonathan Sauer 13 Dec '07

13 Dec '07

Okay, this is weird (and long), but it gets clearer near the end: The following test using lpeg to split a comma-separated values works perfectly (never mind that subpattern B does not do anything): ---------------------------------------------------------------------- % A: % \catcode`\:=11 % \def\FM:ifFileIncluded#1{\message{whatever}} % % \FM:ifFileIncluded{} \directlua0{\unexpanded{ whiteSpace = lpeg.S(" \t\n") splitComma = lpeg.P({ lpeg.Ct(lpeg.V("elem") * (lpeg.V("sep") * lpeg.V("elem"))^0), sep = lpeg.S(",{}"), elem = whiteSpace^0 * lpeg.C((1 - lpeg.V("sep"))^1) * whiteSpace^0, % B }) }} \def\splitComma#1{% \directlua0{% local s = '\luaescapestring{\unexpanded{#1}}' local t = lpeg.match(splitComma,s) for k,v in ipairs(t) do texio.write_nl('[' .. v .. ']') end }% } \splitComma{A, B, C, D, E, F} % `print' is not documented, but prints a compiled pattern's bytecode % to the console \directlua0{lpeg.print(splitComma)} \end ----------------------------------------------------------------------- The pattern created is: [1 = elem 2 = sep 3 = elem 4 = sep ] 00: call -> 2 01: jmp -> 51 02: opencapture table(n = 0) (0) 03: call -> 10 04: choice -> 8 (0) 05: call -> 41 06: call -> 10 07: partial_commit -> 5 08: closecapture close(n = 0) (0) 09: ret 10: span [(09-0a)(20)] 19: opencapture simple(n = 0) (0) 20: choice -> 23 (0) 21: call -> 41 22: failtwice 23: any * 1 24: choice -> 30 (0) 25: choice -> 28 (0) 26: call -> 41 27: failtwice 28: any * 1 29: partial_commit -> 25 30: closecapture close(n = 0) (0) 31: span [(09-0a)(20)] 40: ret 41: set [(2c)(7b)(7d)] 50: ret 51: end However, if I run this with my own format, the pattern is: [1 = elem 2 = sep 3 = elem 4 = sep ] 00: call -> 2 01: jmp -> 51 02: opencapture table(n = 0) (0) 03: call -> 10 04: choice -> 8 (0) 05: call -> 41 06: call -> 10 07: partial_commit -> 5 08: closecapture close(n = 0) (0) 09: ret 10: span [(0a)(20)(2e)(42)(45)(49)(4c-4d)(4f-50)(53)] 19: opencapture simple(n = 0) (0) 20: choice -> 23 (0) 21: call -> 41 22: failtwice 23: any * 1 24: choice -> 30 (0) 25: choice -> 28 (0) 26: call -> 41 27: failtwice 28: any * 1 29: partial_commit -> 25 30: closecapture close(n = 0) (0) 31: span [(0a)(20)(2e)(42)(45)(49)(4c-4d)(4f-50)(53)] 40: ret 41: set [(2c)(7b)(7d)] 50: ret 51: end So instead of checking for whitespace in instructions 10 and 31, input is checked against the character set "\n .BEILMOPS" (and splitting the list fails almost completely). I know what a "Beil" is (an axe), and I know what a "Mops" is (some kind of weird animal, a bit like a groundhog [think Bill Murray]), but what is a "Beilmops"? And a "dot Beilmops"? Is is written in C# or what? Now you'll say "yeah, sure, who cares what weird stuff that weird Jonathan does in that weird format of his", but: This only happens if a macro "\FM:ifFileIncluded" is defined or referenced. If this macro is called "\FM:ifFileLoadeded" (the same length) or "\FM:ifFileIlcluded" ("l" instead of "n"), the pattern is compiled correctly. "\FM:ifFileLncluded" works, too. But the moment a control sequence called "\FM:ifFileIncluded" is used (defined or referenced), the lpeg pattern contains that strange animal. I tried to use Lua state 1 instead of 0 to make sure there were no definitions that could create a side-effect, but the pattern remained the same. I tried to uncomment (A) in above PlainTeX code, but the pattern is still correct. So I first suspected some kind of overflow in TeX's hash table that only occurs when there already exist a lot of control sequences and one of them has a very specific name and thus hash value (this does not seem to be the case, though). I tried moving the definition of "\FM:ifFileIncluded" to the beginning of my format (right after setting the catcodes), but without success. I tried defining it in the PlainTeX format, but again to no avail. I tried removing all unnecessary files from my format, with the same result. More weirdness that I more or less accidentally stumbled upon: \directlua1{\unexpanded{lpeg.print(lpeg.S(" \t\n"))}} results in set [(0a)(20)(2e)(42)(45)(49)(4c-4d)(4f-50)(53)] which is wrong, but \directlua1{\detokenize{lpeg.print(lpeg.S(" \t\n"))}} results in set [(09-0a)(20)] which is correct. And the equivalent, but slightly longer \directlua1{lpeg.print(lpeg.S(" \string\t\string\n"))} again results in the correct set [(09-0a)(20)] And indeed: If I replace "\unexpanded" in the code example above by "\detokenize" (and remove the empty lines which for some reason result in "\par" when "\detokenize" is used, but not with "\unexpanded"), the pattern is compiled correctly and works as expected. The plot thickens. Let's look further; how about simply telling Lua to print the string " \t\n"? \directlua1{\detokenize{texio.write_nl("[ \t\n]")}} results in [ ] but \directlua1{\unexpanded{texio.write_nl("[ \t\n]")}} results in [ IMPOSSIBLE. ] Not so weird anymore: "IMPOSSIBLE." is printed by procedure "print_cs" in luatex.web if the control sequence's pointer is below "active_base", that is zero or negative, or >= the pointer to the undefined control sequence (at least as far as I understand it). And "IMPOSSIBLE." sorted and stripped of duplicates is ... ".BEILMOPS"! Also note that "\t" is defined in PlainTeX, but not in my format. If I define it at the beginning of the code example above, nothing changes. But if I define it before defining "\FM:ifFileIncluded", everything works as expected, and \directlua1{\unexpanded{texio.write_nl("[ \t\n]")}} results in [ ] Not "IMPOSSIBLE." anymore. Now: If the control passed to "print_cs" (or "tokenlist_to_cstring" in luatoken.c) is undefined, "IMPOSSIBLE." is printed. As "\t" is indeed undefined, this is completely expected. What's not expected, is that this only happens if the macro "\FM:ifFileIncluded" is not defined before "\t" is defined (if at all). And weird again: "\n" is defined by neither PlainTeX nor my format, but does not result in "IMPOSSIBLE.". Side note: \immediate\write16{\detokenize{[ \t\n]}} \immediate\write16{\unexpanded{[ \t\n]}} both correctly display "[ \t \n ]". So it seems that "\unexpanded" works as expected, but something else does not. And finally: If I say "\let\t\t" at the beginning of my format, everything works as well. So "\t" may well be undefined, as long as it is entered into TeX's hash table before "\FM:ifFileIncluded" is. Jonathan

6 28

Cron <luatex@www> /var/www/luatex.org/www/bin/luatex-svn
by root＠www.bittext.nl 13 Dec '07

13 Dec '07

U svn/trunk/src/texk/web2c/luatexdir/luatex.web U svn/trunk/src/texk/web2c/luatexdir/font/luafont.c U svn/trunk/manual/luatexref-t.tex U svn/trunk/manual/luatexref-t.pdf Checked out revision 966.

1 0

Cron <luatex@www> /var/www/luatex.org/www/bin/luatex-svn
by root＠www.bittext.nl 12 Dec '07

12 Dec '07

U svn/trunk/src/texk/web2c/luatexdir/luatex.ch U svn/trunk/src/texk/web2c/luatexdir/luatex.web U svn/trunk/src/texk/web2c/luatexdir/lua/luatoken.c U svn/trunk/src/texk/web2c/luatexdir/tex/texnodes.c U svn/trunk/manual/luatexref-t.tex U svn/trunk/manual/luatexref-t.pdf Checked out revision 962.

1 0

More additions to the manual
by Jonathan Sauer 12 Dec '07

12 Dec '07

Hello, some more additions to the manual, diff against 954. Jonathan

1 0

beta 0.20.1 released
by Taco Hoekwater 12 Dec '07

12 Dec '07

Hi all, I have just uploaded the archives for luatex 0.20.1. This is a bugfix release for wednesday's beta, and it fixes the following issues: * texlua was broken on Solaris because the some C header files were loaded in the wrong order. * os.tmpdir() now accepts an argument, making it easier to use. It now generates more unique filenames when it is called repeatedly in one run. * The --luaconly commandline switch is now documented in the --help text. * The new extended hyphenation exceptions were severely broken. * \pdfprotrudechars could cause luatex to abort with an assertion failure. * There was a bug in the \span code that could cause endless loops. * The simple forms of \leaders were messed up on windows because a variable was not properly initialized. * Non-grouped \textdir commands created invalid output. * e-TeX's pseudo files were not closed properly in ini mode. * The luatex.web now weaves properly again. * I made some small improvements to the manual. I have uploaded source and linux/win32 binaries to http://foundry.supelec.fr/projects/luatex/ Have fun, Taco _______________________________________________ dev-luatex mailing list dev-luatex(a)ntg.nl http://www.ntg.nl/mailman/listinfo/dev-luatex

3 7

Cron <luatex@www> /var/www/luatex.org/www/bin/luatex-svn
by root＠www.bittext.nl 11 Dec '07

11 Dec '07

U svn/trunk/src/libs/lua51/llimits.h U svn/trunk/src/libs/lua51/luaconf.h U svn/trunk/src/texk/web2c/luatexdir/luatex.web U svn/trunk/src/texk/web2c/luatexdir/lua/ltexlib.c U svn/trunk/src/texk/web2c/luatexdir/lua/lnodelib.c U svn/trunk/src/texk/web2c/luatexdir/tex/texnodes.c Checked out revision 958.

1 0

Module searching
by Heiko Oberdiek 11 Dec '07

11 Dec '07

Hello, in the TeX world scripts are usually installed below TDS:scripts. Lua does know a module system. Example: There is a package "foobar" with module "foobar.hello". Lua then searches in some standard places for foobar/hello.lua However LuaTeX neglects the texmf trees. Thus "package.loaders" could be extended by a kpse loader, e.g.: function kpse.module_loader(module) local file if string.find(module, ".", 1, true) then -- What to do? -- the following is just an unreliable emergency workaround: module = string.gsub(module, "^.*\%.", "") file = kpse.find_file(module .. ".lua", "texmfscripts") else file = kpse.find_file(module .. ".lua", "texmfscripts") end if file then local loader, error = loadfile(file) if loader then return loader end return "\n\t KPSE loading error:\n" .. error end return "\n\t KPSE search failed" end table.insert(package.loaders, kpse.module_loader) However, the problem are modules with dots. I haven't find a solution using kpse functions. kpsewhich --format=texmfscripts foobar/hello.lua doesn't find the file. Perhaps a search path could be hacked by using the output of kpsewhich --show-path=texmfscripts and appending the module directories to each path component. But: * LuaTeX's kpse library doesn't have a "show_path" function. * os.execute is not available in safer mode. * Last but not least, a kpse function is missing for searching along the modified path specification. * Portability among different operating systems. (directory specificator, ..., LUA_DIRSEP isn't available, ...) Ideas? Something like "foobar_hello.lua" isn't the best solution: * Redundancy in the full name: TDS:scripts/foobar/foobar_hello.lua * It doesn't scale well, e.g. it pollutes "package.loaded". Yours sincerely Heiko <oberdiek(a)uni-freiburg.de>

4 10

Cron <luatex@www> /var/www/luatex.org/www/bin/luatex-svn
by root＠www.bittext.nl 11 Dec '07

11 Dec '07

U svn/trunk/src/texk/web2c/luatexdir/lua/ltexiolib.c U svn/trunk/manual/luatexref-t.tex U svn/trunk/manual/luatexref-t.pdf Checked out revision 955.

1 0