24 Jan 22:25
Cron <luatex <at> boekplan> /var/www/luatex.org/www/bin/luatex-svn
svn: OPTIONS of 'http://foundry.supelec.fr/svn/luatex': could not connect to server (http://foundry.supelec.fr)
svn: OPTIONS of 'http://foundry.supelec.fr/svn/luatex': could not connect to server (http://foundry.supelec.fr)
svn: OPTIONS of 'http://foundry.supelec.fr/svn/luatex': could not connect to server (http://foundry.supelec.fr)
svn: OPTIONS of 'http://foundry.supelec.fr/svn/luatex': could not connect to server (http://foundry.supelec.fr)
svn: OPTIONS of 'http://foundry.supelec.fr/svn/luatex': could not connect to server (http://foundry.supelec.fr)
svn: OPTIONS of 'http://foundry.supelec.fr/svn/luatex': could not connect to server (http://foundry.supelec.fr)
svn: OPTIONS of 'http://foundry.supelec.fr/svn/luatex': could not connect to server (http://foundry.supelec.fr)
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
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
(Continue reading)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@... ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------
>> 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{
(Continue reading)------------------------------------------------------------------------ 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 ------------------------------------------------------------------------
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 |
RSS Feed16 | |
|---|---|
21 | |
19 | |
10 | |
18 | |
41 | |
32 | |
65 | |
14 | |
63 | |
15 | |
50 | |
95 | |
33 | |
109 | |
83 | |
49 | |
29 | |
40 | |
90 | |
127 | |
49 | |
60 | |
114 | |
137 | |
41 | |
24 | |
47 | |
85 | |
131 | |
72 | |
125 | |
119 | |
64 | |
161 | |
173 | |
12 | |
80 | |
58 | |
6 | |
61 |