- dev-luatex - NTG Mailing Lists

LuaTeX manual cannot be searched
by Jonathan Sauer 16 Aug '07

16 Aug '07

Hello, when I search the LuaTeX manual in Acrobat Reader 8 or Apples Preview.app bundled with OS X 10.4.2, I never get any results, even if the word I am searching for definitely exists (since I can read it on the page). Copying from the manual does not work as well; only some weird vertical slashes are copied. Jonathan

2 1

Re: [Dev-luatex] Example: Sorting in LuaTeX
by Jonathan Sauer 15 Aug '07

15 Aug '07

Hello, > > yesterday I experimented a little with \directlua, and I decided to > > code a sorting routine, since sorting in TeX (as i.e. > > implemented in the experimental LaTeX 3 code or in Bernd > > Raichle's paper "Sorting in TeX's mouth") is quite slow. > > Yes, excellent example and nicely emphasizing my comment > during Taco's talk in San Diego: "Doing [list processing] in > TeX is great for your ego, I concur. It is a great feeling when you finally found an elegant (well, relatively elegant, we're talking about TeX's macro language) way of implementing a macro. BTW: Is there a transcript of the video available? The video itself is a little bit too large for me (and possibly others) to download. Also, I find it easier to read a text than to listen to a talk. Faster, too. > but..." No buts! ;-) > > In any case: Imagine the possibilities when using Lua not only for > > manipulating the node list, but also for parsing user input! > > Using lua to parse user input is convenient, think of key=val > processing which is currently jumping through hoops to remove > spaces and the correct number of braces etc. Yes, but until LuaTeX is out of beta and widespread, it will be necessary to keep an implementation in TeX. So unless it really speeds things up, or makes better error handling possible, I do not see much use in parsing user input in Lua. Or am I forgetting something? Jonathan

2 1

Cron <luatex@server> /home/luatex/luatex-svn
by root＠aanhet.net 15 Aug '07

15 Aug '07

U luatex/trunk/src/libs/luafontforge/fontforge/fontforge/parsettf.c Checked out revision 670.

1 0

Cron <luatex@server> /home/luatex/luatex-svn
by root＠aanhet.net 14 Aug '07

14 Aug '07

U luatex/trunk/src/libs/luafontforge/src/luafflib.c U luatex/trunk/src/libs/luafontforge/fontforge/Unicode/gwwiconv.c U luatex/trunk/src/libs/luazlib/lzlib.c Checked out revision 669.

1 0

compiling luatex with --with-system-zlib
by Norbert Preining 14 Aug '07

14 Aug '07

Hi Taco, I am trying to compile luatex with --with-system-zlib (in Debian we have to do this). But the latest changes (from 0.10.1 to 0.10.2) in luatexlib.mk seemed to have messed this up. I get a nice error: ... cd ../../libs/zziplib/zzip && \ make CC='gcc' CFLAGS='-g -O2 ' LDFLAGS='' libzzip.la cp: cannot stat `../../libs/zlib/*.a': No such file or directory make: *** [../../libs/zziplib/zzip/.libs/libzzip.a] Error 1 I reverted luatexlib.mk to (quasi) 0.10.1 (some make -> $(MAKE) replacements I left) and it again compiles. Interestingly, with --with-system-zlib, I also had to add another patch because zzlib or whoever is very picky about the version string: (in luazlib/lzlib.c) if (strcmp(version, ZLIB_VERSION)) then bail out but zlibVersion is (here) 1.3.3, while ZLIB_VERSION is 1.3.3.2. So I changed the code to compare only the first 5 chars: if (strncmp(version, ZLIB_VERSION, 5)) All this together let me compile 0.10.2 with the system zlib. (BTW: I have made all the other libs shared linked, too, freetype, fontconfig, jpeg, etc). If you have any other suggestion or idea, please let me know. I would prefer NOT to patch the luatexlib.mk in that way ... Thanks a lot and all the best 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 ------------------------------------------------------------------------------- ESHER (n.) One of those push tapes installed in public washrooms enabling the user to wash their trousers without actually getting into the basin. The most powerful esher of recent years was 'damped down' by Red Adair after an incredible sixty-eight days' fight in Manchester's Piccadilly Station. --- Douglas Adams, The Meaning of Liff

2 3

Cron <luatex@server> /home/luatex/luatex-svn
by root＠aanhet.net 14 Aug '07

14 Aug '07

U luatex/trunk/manual/luatexref-t.tex Checked out revision 666.

1 0

Assignments in TeX's mouth, or: "Dr. Zaius, it can talk!"
by Jonathan Sauer 14 Aug '07

14 Aug '07

Hello, normally, TeX cannot perform assignments in the mouth (except for \let-ing a previously undefined control sequence to \relax when using \csname...\endcsname). With LuaTeX, this has changed, albeit in a slightly weird way: All assignments are \global. Plain example (with some variations on a theme): ---------------------------------- CUT ------------------------------ \tracingassigns1 % Access internal control sequences: \catcode`@=11 % For easier logging: \def\log#1{\immediate\write\sixt@@n{#1}} \let~\space \count@=5 \log{Before:~~~~~~~~~~~~~~~~~~~\the\count@} % We only define \test, we do not execute it: \begingroup \edef\test{% \directlua0{% % Note that `tex.count.count@' (syntactic sugar for the code % below) cannot be used, since `@' is not a letter and thus % not part of an identifier: tex.count["count@"]=42 % We create some contents for \test: tex.print("Contents of test") }% } % Behold: We changed \count@ in the mouth! \log{After:~~~~~~~~~~~~~~~~~~~~\the\count@} % Note that \test only contains the string passed to tex.print above. % The rest of the Lua code has been executed completely: \log{\string\test~is:~~~~~~~~~~~~~~~~~\meaning\test} \endgroup % Now that is weird: Assigning registers in Lua is automatically % global: \log{After \string\endgroup:~~~~~~~~~~\the\count@} % We try again, without \edef: \begingroup \directlua0{tex.count["count@"]=23} \log{In group, 2nd try:~~~~~~~~\the\count@} \endgroup % The assignment is global again: \log{After \string\endgroup, 2nd try:~\the\count@} % We try again, using accessor functions: \begingroup \directlua0{tex.setcount("count@",17)} \log{In group, 3rd try:~~~~~~~~\the\count@} \endgroup % And global again: \log{After \string\endgroup, 3rd try:~\the\count@} % We try again, using accessor functions and \{b,e}group: \bgroup \directlua0{tex.setcount("count@",37)} \log{In group, 3rd try:~~~~~~~~\the\count@} \egroup % And still global: \log{After \string\endgroup, 3rd try:~\the\count@} \bye ---------------------------------- CUT ------------------------------ Note: According to the Lua reference manual, section 2.1, the definition of `letter' depends on the current locale. Would it be possible/sensible to define the current locale not according to the system TeX is run on (which would actually make LuaTeX code locale-dependent, since some identifiers might not work on another computer with a different locale) according to TeX's current catcode table? And while we're at it: Should string.uppercase and string.lowercase use the \lccode/\uccode tables? When tracing assignments, the ones made from Lua are flagged as being \global (BTW: What are these messages about `reassigning [no_local_whatsits]'?): ---------------------------------- CUT ------------------------------ This is luaTeX, Version 3.141592-beta-0.10.2-2007081018 (Web2C 7.5.6) (format=luatex 2007.8.10) 11 AUG 2007 08:50 **MouthSideeffect (MouthSideeffect.tex{into \tracingassigns=1} {changing \log=macro:->\mathop {\rm log}\nolimits } {into \log=macro:#1->\immediate \write \sixt@@n {\ETC.} {changing ~=macro:->\penalty \@M \ } {into ~=macro:-> } {changing \count255=92} {into \count255=5} Before: 5 {reassigning [no_local_whatsits]=0} {reassigning [no_local_dirs]=0} {globally changing \count255=5} {into \count255=42} {changing \test=undefined} {into \test=macro:->Contents of test} After: 42 \test is: macro:->Contents of test After \endgroup: 42 {reassigning [no_local_whatsits]=0} {reassigning [no_local_dirs]=0} {globally changing \count255=42} {into \count255=23} In group, 2nd try: 23 After \endgroup, 2nd try: 23 {reassigning [no_local_whatsits]=0} {reassigning [no_local_dirs]=0} {globally changing \count255=23} {into \count255=17} In group, 3rd try: 17 After \endgroup, 3rd try: 17 {reassigning [no_local_whatsits]=0} {reassigning [no_local_dirs]=0} {globally changing \count255=17} {into \count255=37} In group, 3rd try: 37 After \endgroup, 3rd try: 37 ) No pages of output. ---------------------------------- CUT ------------------------------ I do not think that assignments to TeX's registers done in Lua code should be automatically \global, as it makes writing macros without (intentioned) side-effects much harder. And those macros are the best, since they can be used anywhere without having to remember that they clobber register \foo, redefine macro \bar et cetera. So, returning to this mail's subject, I can only say: "Take your hands off my grouping, you damn dirty Lua code!" ;-) Jonathan

3 10

Beta 0.10.2
by Taco Hoekwater 14 Aug '07

14 Aug '07

Hi, Yesterday evening I released a new beta, but I could not send any email then, so here it is. This release fixes a number of bugs in 0.10.1, but does not do much else. Bugs fixed: * the primitive \span was completely broken * \pdfexpandfont (font expansion) misbehaved if it was used more than once * virtual fonts: sometimes they used the wrong internal font id, loading vf fonts via fonts.read_vf() was impossible, and sometimes virtual fonts created segfaults * while dumping formats, the last font parameter for each font was not dumped at all * zziplib was always compiled with pre-installed zlib headers, instead of the ones in the build tree * lua 5.1.2 has trouble quoting ^Z characters etc, the tentative patch for lua 5.2 from Luiz fixes that, hopefully * fontforge.font('font.pfb') now properly parses AFM boundingboxes * non-existing files in the argument for fontforge.open() or fontforge.info() could cause segfaults, now it generates an error instead * fontforge.open() did not return character widths for vertical fonts as it should * on Windows, fontforge believed that ttc files (TrueType Collections) were actually directories. ttc processing is still not 100% correct, but it is getting better * the build system used explicit 'make' sometimes * the auto-growing string pool was not used everywhere * there were some typos in the documentation parts of the pascal web * use of \parshape could easily exhaust all available memory New features: * support for applying Adobe Feature files (.fea) and Adobe Font Metrics (.afm) is added to the fontforge library * fontforge.info() will now return an array of tables for the contents for ttc files * support for a 'texluac' personality was added, to replace the 'luac' command from the official Lua distribution The download url is: http://foundry.supelec.fr/projects/luatex/ Best wishes, Taco

1 0

FYI: Encoding mappings
by Jonathan Sauer 14 Aug '07

14 Aug '07

Hello, since LuaTeX only reads files in UTF-8 encoding, other encodings have to be converted. Taco provided the necessary code in his mail of the 09 December 2006, but only for ISO-Latin-2. The mappings for other encodings are available from Unicode.org, though, at <http://www.unicode.org/Public/MAPPINGS/>. Maybe you already know this. Maybe it helps. Jonathan

1 0

Strange clipped text and overfull hboxes
by Jonathan Sauer 14 Aug '07

14 Aug '07

Hello, expanding on yesterday's message about font expansion in LuaTeX beta 0.10.1, I verified the phenomenon of text being typeset in a narrow column and clipped at the left margin. Then I dug deeper into it. Then I remembered Colonel Kurtz in "Apocalypse Now": "The horror, the horror ..." ;-) Situation: teTeX 3.0 on a macintosh (PPC) with a new pdfeTeX (1.40.3) and LuaTeX beta 0.10.1 (both built by myself). The HOMETEXMF path in texmf.cnf is "/Volumes/Dummy;/Volumes/Work/Workplace/Writing/TeX;/usr/local/ teteX/and/so/on". In the second path element, the formats for both LuaTeX and pdfeTex are stored, along with some other files (formats, log files). The first path element does not exist (just a dummy for testing the phenomenon). If the number of visible files in the directory the luatex.fmt file is stored in is equal to six or lower, some strange overfull boxes are reported by LuaTeX, and the text is typeset as described above. See attached log file "Six_LuaTeX.console.log". "Six_web2c.listing.txt" is the directory listing of the directory the formats are stored in. If the number of visible files in the directory is seven, everything works perfectly. See attached log file "Seven_LuaTeX.console.log" and "Seven_web2c.listing.txt". It seems that the error occurs if the number of (visible) files in the directory is even or less than six. Note that the error also seems to depend on which path element in HOMETEXMF points to the format directory. If it is the first path element, the error seems to occur if the number of (visible) files in the directory is odd or less than seven. The issue is not a corrupt file system; I created a small partition for the test (no big deal, I head a little bit of free space on my HD) and also verified the file system integrity. Now, normally I would say that there is something really, really wrong with my TeX setup -- but in pdfeTeX, everything works perfectly (pdfetex.fmt in the same place as luatex.fmt, same test file; see "Six_pdfTeX.console.log" and "Seven_pdfTeX.console.log"). This IMO points to LuaTeX. Or am I missing something? I have not yet had the time to look into the source code. The following is a small Plain-based document which demonstrates the behaviour: ------------------------------ CUT ------------------------------- \pdfoutput1 % The following text is typeset correctly: Hello {\tentt world} with Lua\TeX. Hello {\tentt world} with Lua\TeX. Hello {\tentt world} with Lua\TeX. Hello {\tentt world} with Lua\TeX. Hello {\tentt world} with Lua\TeX. Hello {\tentt world} with Lua\TeX. Hello {\tentt world} with Lua\TeX. Hello {\tentt world} with Lua\TeX. % The following text is typeset in a narrow column and cut off at the % left. This is just {\tentt test}. Just a {\tentt test}. Nothing more than a {\tentt test}. Just a {\tentt test}. Nothing more than a {\tentt test}. Just a {\tentt test}. Nothing more than a {\tentt test}. Just a {\tentt test}. Nothing more than a {\tentt test}. Just a {\tentt test}. Nothing more than a {\tentt test}. Just a {\tentt test}. Nothing more than a {\tentt test}. % The following text is typeset in a narrow column as well: This is just test. Just a test. Nothing more than a test. Just a test. Nothing more than a test. Just a test. Nothing more than a test. Just a test. Nothing more than a test. Just a test. Nothing more than a test. Just a test. Nothing more than a test. % The following *was* typeset across the whole page, until I added % the `-- not' et cetera: Some more text, just to check if the weird typesetting of the last paragraph can be repeated. Still, it would be strange if not. But it looks like -- not, at least if the paragraph is short. If it is longer, the text is typeset incorrectly. % The following is typeset across the whole page, just like it should % be: But only if the paragraph is a little bit longer, a few lines. \bye ------------------------------ CUT ------------------------------- Sorry for posting this weird bug (if it is a bug). I know how difficult it is to track these phenomenons down. Jonathan

3 8