Graham Douglas wrote:
Hi Taco
I have been experimenting with external C libraries by writing
Lua bindings under Windows --- DLLs.
I have noticed something I'd like to ask about ---
to know if it is expected behavior.
When these DLLs return text I'm doing a lot of tex.write(...)
of the data r
r3614 | taco | 2010-04-13 18:45:00 +0200 (Tue, 13 Apr 2010) | 2 lines
Changed paths:
M /branches/0.60.x/source/texk/web2c/Makefile.am
M /branches/0.60.x/source/texk/web2c/Makefile.in
M /branches/0.60.x/source/texk/web
Patrick Gundlach wrote:
Hi (Taco),
the function tex.linebreak() is mentioned in the manual, but the
defaults are not. Are the ones in the tracker item #340 still valid?
Could it be that the default value for linepenalty is not taken into
account? That means: if you set \linepenalty=0 from TeX,
Hi (Taco),
the function tex.linebreak() is mentioned in the manual, but the defaults are
not. Are the ones in the tracker item #340 still valid?
Could it be that the default value for linepenalty is not taken into account?
That means: if you set \linepenalty=0 from TeX, tex.linebreak() behaves
Hi Taco
I have been experimenting with external C libraries by writing
Lua bindings under Windows --- DLLs.
I have noticed something I'd like to ask about ---
to know if it is expected behavior.
When these DLLs return text I'm doing a lot of tex.write(...)
of the data returned from the DLL func
r3611 | oneiros | 2010-04-12 22:26:02 +0200 (Mon, 12 Apr 2010) | 3 lines
Changed paths:
M /trunk/source/texk/web2c/Makefile.in
M /trunk/source/texk/web2c/luatexdir/ChangeLog
M /trunk/source/texk/web2c/luatexdir/am/lib
