- dev-luatex - NTG Mailing Lists

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

23 Jan '12

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

1 0

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

23 Jan '12

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

1 0

Has the development stopped?
by Christoph Pohl 17 Jan '12

17 Jan '12

Hello, I’ve noticed that there hasn’t been any SVN activity since October. Is this some sort of "scheduled break" or did you loose interest? I think luatex is an awesome idea, and I’m really grateful for all the great work you guys have done so far. It would be a real tragedy if it never reaches 1.0. I’m not sure I can help with the actual coding, but I’d love to help out with if I can. Cheers Christoph

3 3

string.explode()
by Reinhard Kotucha 02 Jan '12

02 Jan '12

Hi Taco, though luatex isn't frozen yet, I think that many people are using it already and drastic changes are not desirable. There is one thing which could probably be improved without breaking existing scripts, as far as I can see: string.explode(foo, ' +') expects that ' ' is a space token (ASCII 0x20). Is it possible to change string.explode() so that ' ' can be either a space token (ASCII 0x20) or a tabulator (ASCII 0x09) without breaking existing scripts? Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------

3 3

Memory allocation bugs?
by Vianney le Clément 02 Jan '12

02 Jan '12

Hello, Recently, I have run into strange error messages using plain luatex. I have narrowed it down to some minimal examples shown below with their log. I have tried luatex provided by texlive 2011 and a build from the latest svn trunk. They work fine with pdftex. They also work fine (apart from luatex being unable to ship the huge page) when removing the \font\temp=... line in the loop. In case you wonder, my intent is not to put 10k lines on one page, it just simplifies the examples. I also get the errors when spreading out the text across multiple pages. Can you put me in CC of the replies as I'm not subscribed to the list? Thanks. Best wishes for 2012, Vianney ---- \pdfmapline{phvr8r Helvetica 32 <8r.enc} \font\tenpt=phvr8r at 10pt \newbox\outbox \newcount\Line \Line=0 \loop\ifnum\Line<12000 \font\temp=phvr8r at 10pt \setbox0=\hbox{\tenpt The quick brown fox jumps over the lazy dog} \setbox\outbox=\vbox{\unvbox\outbox\box0} \advance\Line by 1 \repeat \shipout\box\outbox \bye ---- This is LuaTeX, Version beta-0.71.0-2011123118 (format=luatex 2011.8.17) 1 JAN 2012 12:53 restricted \write18 enabled. **double-free-node.tex (./double-free-node.tex \outbox=\box16 \Line=\count27 [1] ! Attempt to double-free hlist node 57582, ignored. l.14 \shipout\box\outbox ? X {/opt/texlive/2011/texmf-dist/fonts/enc/dvips/base/8r.enc} Output written on double-free-node.pdf (1 page, 67114 bytes). PDF statistics: 12 PDF objects out of 1000 (max. 8388607) 8 compressed objects within 1 object stream 0 named destinations out of 1000 (max. 131072) 1 words of extra memory for PDF output out of 10000 (max. 10000000) ---- ---- \pdfmapline{phvr8r Helvetica 32 <8r.enc} \newbox\outbox \newcount\Line \Line=0 \loop\ifnum\Line<12000 \font\temp=phvr8r at 10pt \setbox0=\hbox{The quick brown fox jumps over the lazy dog} \setbox\outbox=\vbox{\unvbox\outbox\box0} \advance\Line by 1 \repeat \shipout\box\outbox \bye ---- This is LuaTeX, Version beta-0.71.0-2011123118 restricted \write18 enabled. (./segfault.texSegmentation fault ---- ---- \pdfmapline{phvr8r Helvetica 32 <8r.enc} \newbox\outbox \newcount\Line \Line=0 \loop\ifnum\Line<10000 \font\temp=phvr8r at 10pt \setbox0=\hbox{Test-test (test test), test test test test test test'!" Test } \setbox\outbox=\vbox{\unvbox\outbox\box0} \advance\Line by 1 \repeat \shipout\box\outbox \bye ---- This is LuaTeX, Version beta-0.71.0-2011123118 (format=luatex 2011.8.17) 1 JAN 2012 12:51 restricted \write18 enabled. **copy-free-node.tex (./copy-free-node.tex \outbox=\box16 \Line=\count27 ! Attempt to copy free hlist node 5549, ignored. \body ... \setbox 0=\hbox {Test-test (test test), test test test test test t... \next ->\body \let \next \iterate \else \let \next \relax \fi \next l.12 \repeat ? X No pages of output. PDF statistics: 0 PDF objects out of 1000 (max. 8388607) 0 named destinations out of 1000 (max. 131072) 1 words of extra memory for PDF output out of 10000 (max. 10000000) ----

2 1

Re: [Dev-luatex] [lltx] \scantokens differs between LaTeX and plain?
by Martin Schröder 16 Nov '11

16 Nov '11

2011/11/15 Heiko Oberdiek <heiko.oberdiek(a)googlemail.com>: > As result of "pdftex --ini --etex" macro:->a b is printed. > "luatex --ini --etex" breaks with an error: > > Runaway definition? > ->a > ! File ended while scanning definition of \x. > <inserted text> > } > l.9 \edef\x{\scantokens{a > b\noexpand} > } > ? Thanks; I've opened an bug report at http://tracker.luatex.org/view.php?id=733 Best Martin

1 0

The explanation of \directlua in the manual
by Javier Múgica de Rivera 20 Oct '11

20 Oct '11

>> Note that the expansion of \directlua is a sequence of characters, not >> of tokens, contrary to all TeX commands. So formally speaking its >> expansion is null, but places material on a pseudo-file to be >> immediately read by TeX, as etex's \scantokens. >> >> For a description of print functions look at section 4.13.10. >Is that really true? When you assign catcodes (catcode tables) to the print functions, >TeX's behavior is different from scantokens. I have never used scantokens, so I am >not 100% sure. Take for example: > >tex.print(-2, "\\def\\foo{abc}") > >will not define \foo. While you have referenced the section with the print commands, I >think that the description is misleading. > >Patrick The section on print commands says: "The arguments to these three functions are all stored in an in-memory virtual file that is fed to the TEX scanner as the result of the expansion of \directlua." An so what is fed to TEX are characters, no tokens. Your example, indeed, is a good one to exhibit that behaviour. The fact that you can change the catcodes and read the string again shows that TEX reads characters, tokenizing them. If it where not and the expansion were a sequence of tokens then \foo would get defined. Your example is like \def\scanasothers#1{ <set up catcodes as the value -2 for the first argument of tex.print does> \scantokens{#1} <reset catcodes> } \scanasothers{def\foo{abc}} This actual example suffices: \def\scanasothers#1{ \catcode`\\=12 \scantokens{#1} \catcode`\\=0 } \scanasothers{\def\foo{abc}} \show\foo \end Which reports > \foo=undefined. l.8 \show\foo and the dvi output includes the \'s output as " (the character in the font at the position of \). Javier

2 1

The explanation of \directlua in the manual
by Javier Múgica de Rivera 17 Oct '11

17 Oct '11

When I read this from the manual a long time ago: The \directlua command is expandable: the results of the LUA code become effective immediately. I could not make sense of it, and actually cannot up to day. What are "the results of the LUA code"? What does "become effective" mean? Now I now the answers to those questions but not because of the explanation given there. The example provided does not help much either. Note that this comes very soon in the manual. I propose the following wording: The \directlua command is expandable. Since it passes Lua code to the Lua interpreter its expansion from the TeX viewpoint is usually empty. However, there are some Lua functions that produce material to be read by TeX, the so called print functions. The most simple use of these is tex.print(<string> s). The characters of the string s will be placed on TeX input buffer, that is, "before TeX's eyes" to be read by TeX immediately. For example: \count10=20 a\directlua{tex.print(tex.count[10]+5)}b expands to a25b Here is another example: $\pi = \directlua{tex.print(math.pi)}$ will result in p = 3.1415926535898 Note that the expansion of \directlua is a sequence of characters, not of tokens, contrary to all TeX commands. So formally speaking its expansion is null, but places material on a pseudo-file to be immediately read by TeX, as etex's \scantokens. For a description of print functions look at section 4.13.10. Regards, Javier A. Múgica

3 2

Cron <luatex@boekplan> /var/www/luatex.org/www/bin/luatex-svn
by root＠mail.boekplan.nl 14 Oct '11

14 Oct '11

------------------------------------------------------------------------ r4358 | taco | 2011-10-14 10:45:59 +0200 (Fri, 14 Oct 2011) | 2 lines Changed paths: M /trunk/source/texk/web2c/luatexdir/pdf/pdfgen.w M /trunk/source/texk/web2c/luatexdir/tex/filename.w M /trunk/source/texk/web2c/luatexdir/tex/maincontrol.w underscore identifiers patch from minux ------------------------------------------------------------------------

1 0

We no long use Tangle, but the code still contains lot of identifiers with underscores stripped
by minux 14 Oct '11

14 Oct '11

Hi! LuaTeX stopped using tangle long time ago, but identifiers like kpseinitprog, kpsesetprogramenabled, are still in the code. They make the program a little unreadable, so I'm current working on it. I would like to hear any suggestions from you: is it necessary? Best regards, minux.

3 4