July 2008 - dev-luatex - NTG Mailing Lists

Cron <luatex@metatex> /var/www/luatex.org/www/bin/luatex-svn
by root＠www.metatex.org 11 Jul '08

11 Jul '08

U svn/trunk/build.sh.cross U svn/trunk/build.sh.linux U svn/trunk/src/texk/web2c/luatexdir/Makefile.in U svn/trunk/src/texk/web2c/luatexdir/depend.mk D svn/trunk/src/texk/web2c/luatexdir/lua/psout.w D svn/trunk/src/texk/web2c/luatexdir/lua/mp.w D svn/trunk/src/texk/web2c/luatexdir/lua/lmplib.c U svn/trunk/src/texk/web2c/luatexdir/luatexlib.mk A svn/trunk/src/texk/web2c/mpdir A svn/trunk/src/texk/web2c/mpdir/psout.w A svn/trunk/src/texk/web2c/mpdir/configure A svn/trunk/src/texk/web2c/mpdir/mp.w A svn/trunk/src/texk/web2c/mpdir/Makefile.in A svn/trunk/src/texk/web2c/mpdir/tfmin.w A svn/trunk/src/texk/web2c/mpdir/configure.in A svn/trunk/src/texk/web2c/mpdir/depcomp A svn/trunk/src/texk/web2c/mpdir/config.guess A svn/trunk/src/texk/web2c/mpdir/ltmain.sh A svn/trunk/src/texk/web2c/mpdir/config.sub A svn/trunk/src/texk/web2c/mpdir/lmplib.c A svn/trunk/src/texk/web2c/mpdir/config.h.in A svn/trunk/src/texk/web2c/mpdir/mpxout.w A svn/trunk/src/texk/web2c/mpdir/avl.c A svn/trunk/src/texk/web2c/mpdir/mpost.w A svn/trunk/src/texk/web2c/mpdir/avl.h A svn/trunk/src/texk/web2c/mpdir/missing A svn/trunk/src/texk/web2c/mpdir/Makefile.am A svn/trunk/src/texk/web2c/mpdir/memio.w A svn/trunk/src/texk/web2c/mpdir/aclocal.m4 A svn/trunk/src/texk/web2c/mpdir/install-sh U svn/trunk/build.sh Checked out revision 1385.

1 0

Cron <luatex@metatex> /var/www/luatex.org/www/bin/luatex-svn
by root＠www.metatex.org 10 Jul '08

10 Jul '08

U svn/trunk/src/libs/luasocket/src/Makefile U svn/trunk/src/texk/web2c/luatexdir/luatex.web Checked out revision 1383.

1 0

luatex loading old hyphenation patterns
by Norbert Preining 07 Jul '08

07 Jul '08

Hi Taco, hi all, I am trying to activate the latex based fromats of luatex in the Debian packages, but stumbled over problematic hyphenation patterns. Currently, luatex dies on tex/generic/ukrhyph/ukrhypmp.tex as shipped with TL2007, it contains Ukrainian hyphenation patterns in LCY (cp866nav) encoding. I guess that one cannot do anything here but wait for TL2008 with the new utf8 patterns to hit Debian. Right? Best wishes Norbert ------------------------------------------------------------------------------- Dr. Norbert Preining <preining(a)logic.at> Vienna University of Technology Debian Developer <preining(a)debian.org> Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------------- "Yes, it's the right planet, all right," he said again. "Right planet, wrong universe." --- Douglas Adams, The Hitchhikers Guide to the Galaxy

4 5

Cron <luatex@metatex> /var/www/luatex.org/www/bin/luatex-svn
by root＠www.metatex.org 05 Jul '08

05 Jul '08

D svn/trunk/src/texk/web2c/pwd.h U svn/trunk/src/texk/web2c/luatexdir/utils.c U svn/trunk/src/texk/web2c/luatexdir/image/writeimg.c U svn/trunk/src/texk/web2c/luatexdir/depend.mk U svn/trunk/src/texk/web2c/luatexdir/lua/lcallbacklib.c U svn/trunk/src/texk/web2c/luatexdir/lua/luanode.c U svn/trunk/src/texk/web2c/luatexdir/lua/lnodelib.c U svn/trunk/src/texk/web2c/luatexdir/ptexlib.h Checked out revision 1373.

1 0

Re: [Dev-luatex] Q: Why does LuaTeX embed rather than extend?
by Hans Hagen 04 Jul '08

04 Jul '08

Jonathan Fine wrote: > Hello Hans > >> maybe in 2016 we have reached a point that many aspects of tex have >> been rewritten in more independent c modules that then are glued >> together by lua but it does not change the principle ... it's still >> 90% tex then > > Hans, are you saying here that extend would be better, were it not so > much work? Or are you saying something else? I'm not sure. well, we're are quite content with tex as it is but decided it was time to open it up and use lua for that purpose (with the added benefit of a scripting language that can be used for other purposes); there' snothing wrong with tex as it is apart from some things that we wanted to add to it for a long time and the fact that it had to go open type, unicode etc etc our choices are such that no solutions are implemented (this saves much useless discussions that due to conflicting opinions would lead to nothing) but only mechanisms for users (macro package writers) to add functionality to tex; the basic building blocks remain >> also, our choice for lua, as well as the decisions we make are driven >> by respect for tex (as it is), lua as it is, the things that the >> three of us have wanted to see in tex for ages and of course fun > > My question is not about your choice of Lua, but the decision to embed > rather than extend. As I already mentioned, the socket module extends Lua. we use lua as it is meant ... as an extension language sockets are a general purpose library which is quite something different from tex > Here's another example. LuaSQL is an extension of Lua that allows "a > Lua program to connect to ODBC, ADO, Oracle ... databases" and perform > database operations. > http://www.keplerproject.org/luasql/index.html > > LuaSQl is C source that can be compiled to generate a library that can > be linked to the application or dynamically loaded. > http://www.keplerproject.org/luasql/manual.html#compiling > > Providing a typesetting extension to Lua would similarly allow any Lua > program to connect to the typesetting engine and perform typesetting > operations. of the reverse, one can extend luatex to load extra libraries luatex is the core application; just as games that use lua are core applications, and just as adobe does not extend lua with imagine libs but provides an application that uses lua; take fontforge ... it uses python as extension language and remains the core app > [discussion of documentation snipped] > >> well, that would be true for all games that use lua, editors, adobe >> progs etc ... it makes no sense to link all of them together ... you >> miss the whole point lua > > I think it makes perfect sense to link an editor and a typesetting > engine together. And someone writing a 'Learn Mathematics' game might > wish to connect to a typesetting engine. as said, maybe in 2016 we have redone so much that one can think of luatex as a collection of libs, but even then a user needs the application luatex for it to be useful in itself also, we want a stable and well defined next generation tex, which means that luatex has all the libs that we decide to make sense built in (and maintained in the source tree); also, on top of luatex one uses macro packages; luatex in itself is not that useful (btw, if one thinks of lua as a huge collection of libs, then it becomes like perl, python, ruby etc ... big bigger biggest and we enter maintainance, compatibility, distribution etc problems ... again a reason why we used lua as an *extension* language.. small is beautiful) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Q: Why does LuaTeX embed rather than extend?
by Jonathan Fine 03 Jul '08

03 Jul '08

I've got a question about a LuaTeX design decision. I'd like to know why LuaTeX embeds Lua in a typesetting program. Perhaps it could instead have extended Lua with a typesetting module. Here's how to embed Lua (in the host program): http://www.lua.org/manual/5.0/manual.html#3 Here's how to extend Lua (with additional 'builtins'): http://www.lua.org/manual/5.0/manual.html#3.16 Here's an example of a Lua extension: http://www.tecgraf.puc-rio.br/~diego/professional/luasocket/ One of the key difference between embed and extend is that Lua socket "is available to any Lua application once it has been properly initialized by the interpreter in use." LuaTeX, because it embeds Lua, is not be similarly available to other Lua applications. -- Jonathan

3 2

Different results between dvi and pdf modes
by Khaled Hosny 03 Jul '08

03 Jul '08

The following example (from the TeXbook source) works fine in dvi mode, but gives an error in pdf mode: \font\cmman=cmman \line{\cmman The\hfill T\kern-10pt\lower13pt\hbox{E}\kern-5pt Xbook} \bye And the error that I get when I run "luatex --output-format=pdf" (pdftex works fine though): This is LuaTeX, Version snapshot-0.28.0-2008063017 (Web2C 7.5.6) (t.tex [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}]kpathsea: Running mktexpk --mfmode / --bdpi 72 --mag 1+0/72 --dpi 72 cmman mktexpk: Mismatched mode ljfour and resolution 72; ignoring mode. mktexpk: Can't guess mode for 72 dpi devices. mktexpk: Use a config file or option to specify the mode; see: mktexpk: http://tug.org/texinfohtml/kpathsea.html#Unable-to-generate-fonts kpathsea: Appending font creation commands to missfont.log. ) luaTeX warning (file cmman): Font cmman at 72 not found </usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmr10.pfb> Output written on t.pdf (1 page, 3199 bytes). Transcript written on t.log. Regards, Khaled -- Khaled Hosny Arabic localizer and member of Arabeyes.org team

2 1

Cron <luatex@metatex> /var/www/luatex.org/www/bin/luatex-svn
by root＠www.metatex.org 03 Jul '08

03 Jul '08

U svn/trunk/src/texk/web2c/luatexdir/luatex.web U svn/trunk/src/texk/web2c/luatexdir/lua/psout.w U svn/trunk/src/texk/web2c/luatexdir/lua/mp.w U svn/trunk/src/texk/web2c/luatexdir/lua/luanode.c U svn/trunk/src/texk/web2c/luatexdir/ptexlib.h U svn/trunk/manual/luatexref-t.tex Checked out revision 1362.

1 0

Unicode in \pdfinfo
by Khaled Hosny 03 Jul '08

03 Jul '08

\pdfinfo doesn't seem to support Unicode, when I compile the attached example with luatex I get symbols like Ù‡ØµØ© instead of the proper (Arabic) Unicode strings. Shouldn't luatex default to Unicode here too? Regards, Khaled -- Khaled Hosny Arabic localizer and member of Arabeyes.org team

6 24

The current archive is only available to the list members
by Jonathan Fine 03 Jul '08

03 Jul '08

Hello I've been lurking on this list for a couple of months, and it seems to me that it would be really helpful to the TeX and Lua communities if their members could read the messages, without having to subscribe to the list. For what it's worth, I think most open-source devel mailing lists are publicly viewable. I'd like to know what the other list members think. Jonathan

3 4