- dev-luatex - NTG Mailing Lists

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

14 Jul '13

svn: OPTIONS of 'https://foundry.supelec.fr/svn/luatex': Could not resolve hostname `foundry.supelec.fr': Host not found (https://foundry.supelec.fr)

1 0

set exit status
by Patrick Gundlach 12 Jul '13

12 Jul '13

Hi, is it possible to programatically set the exit status of the LuaTeX run? say something like this: tex.exitstatus = 1 or \exitstatus=1 \bye Patrick

3 3

Re: [Dev-luatex] set exit status
by Patrick Gundlach 12 Jul '13

12 Jul '13

Hi Luigi, > is it possible to programatically set the exit status of the LuaTeX run? > > say something like this: > > tex.exitstatus = 1 > > or \exitstatus=1 \bye currently I create a "status file" and parse it after the run. I'd like to signal the parent process if this is really necessary. Patrick

1 0

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

12 Jul '13

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

1 0

How to crop bitmap images
by Patrick Gundlach 02 Jul '13

02 Jul '13

Hi, I'd like to crop a bitmap image. How? This is my code for image inclusion: ------- \directlua{ image = img.scan{filename="hacker.jpg"} tex.box[0] = node.hpack(img.node(image)) } \box0 ------- bbox{...} seems to work only with PDF images. Patrick

2 5

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

14 Jun '13

------------------------------------------------------------------------ r4638 | taco | 2013-06-14 09:44:16 +0200 (Fri, 14 Jun 2013) | 2 lines Changed paths: M /trunk/source/texk/web2c/luatexdir/lua/luainit.w patch from Akira ------------------------------------------------------------------------ r4639 | taco | 2013-06-14 09:45:03 +0200 (Fri, 14 Jun 2013) | 2 lines Changed paths: M /trunk/source/texk/web2c/luatexdir/lua/liolibext.c small patch to popen() args from Akira ------------------------------------------------------------------------

1 0

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

13 Jun '13

------------------------------------------------------------------------ r4637 | taco | 2013-06-13 13:27:34 +0200 (Thu, 13 Jun 2013) | 2 lines Changed paths: M /trunk/source/texk/web2c/luatexdir/lua/luainit.w small changes to invocation name test ------------------------------------------------------------------------

1 0

Cron <luatex@boekplan> /var/www/luatex.org/www/bin/luatex-svn
by root＠mail.boekplan.nl 10 Jun '13

10 Jun '13

------------------------------------------------------------------------ r4636 | taco | 2013-06-10 09:17:23 +0200 (Mon, 10 Jun 2013) | 2 lines Changed paths: M /trunk/manual/luatexref-t.tex remove mention of cidmap file callbacks ------------------------------------------------------------------------

1 0

Unicode in \pdfoutlines
by geradts＠tatzetwerk.nl 29 May '13

29 May '13

Dear LuaTeXies, I have been experimenting with Unicode characters (> 0x00FF) in \pdfoutlines (bookmarks) in (plain)LuaTeX. This post http://www.ntg.nl/pipermail/dev-luatex/2008-July/001694.html helped me to find out that the contents of the pdfoutline will be interpreted as UTF-16 if they are preceded by the BOM 0xFE 0xFF (which in LuaTeX can be output using the 0x1100FE 0x1100FF notation). After this BOM the Greek letter alpha (Unicode 0x03B1) can be presented as 0x110003 0x1100B1. The (very minimal) convertPDFstring function in the sample below takes care of this. However, when trying to present positions < 0x0100 I ran into a problem. It turned out that LuaTeX does not output 0x110000 to the pdf and this is needed for these positions; for example the letter a (0x0061) would be output as 0x110000 0x110061. Is this intended behaviour? The LuaTeX manual seems to present 0x110000 as a valid way to output a byte-sized chunk. > Output in byte-sized chunks can be achieved by using characters just outside of the valid Unicode range, starting at the value 1,114,112 (0x110000). When the time comes to print a character c> = 1,114,112, LuaTEX will actually print the single byte corresponding to c minus 1,114,112. Any suggestions? Best, Ivo. ============================================================================================================ \begingroup \catcode`\%=12 \directlua{ function convertPDFstring(s) tex.write(unicode.utf8.char(0x1100FE, 0x1100FF)) for c in string.utfvalues(s) do tex.write(unicode.utf8.char(0x110000 + c / 256, 0x110000 + c % 256)) end end } \endgroup line 1\pdfdest num 1 xyz\pdfoutline goto num 1 count 0{\directlua{convertPDFstring('αβγāĉđ')}} % works fine line 2\pdfdest num 2 xyz\pdfoutline goto num 2 count 0{\directlua{convertPDFstring('abcdef')}} % not working \bye --- TAT Zetwerk --- Ondiep Zuidzijde 6 3551 BW Utrecht --- t 030 2 456 056 f 030 2 456 336 i www.tatzetwerk.nl e geradts(a)tatzetwerk.nl ---

1 0

Fix for luaotfload on Cygwin
by Ken Brown 22 May '13

22 May '13

There are several problems with luaotfload on Cygwin (detailed below). The short version of this email as that the problems can be fixed by removing all Cygwin-specific code, so that Cygwin is treated like any other unix-like system. The relevant patches are attached. Here are the details, based on the version of luaotfload in the TeX Live 2013 pretest as of today. 1. The code incorrectly assumes that Cygwin is a case-insensitive system. This is not necessarily the true; see http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensi… I and many other Cygwin users have followed these instructions to make Cygwin case sensitive. As a result, luaotfload-tool failed on my system with the cryptic error message ...texmf-dist/tex/luatex/luaotfload/luaotfload-database.lua:921: attempt to index field '?' (a nil value) I finally tracked down the problem to the fact that case was being ignored in the filename /usr/local/texlive/2013/texmf-dist/fonts/opentype/adobe/sourcecodepro/SourceCodePro-Black.otf. 2. The code uses "cygdrive", ignoring the fact that users can change the cygdrive prefix to whatever they want in /etc/fstab. For example, some users prefer to use "mnt". 3. Because the code doesn't use /etc/fonts/fonts.conf, it doesn't add the Cygwin system fonts to the database. 4. Because of the use of os.getenv("WINDIR"), the code produces Windows paths rather than Posix paths when it scans the Windows font directory. This causes a problem as reported in the thread starting at http://cygwin.com/ml/cygwin/2013-04/msg00454.html and continuing at http://cygwin.com/ml/cygwin/2013-05/msg00006.html After my patch is applied, the correct Posix path is used (because it is in /etc/fonts/fonts.conf). Ken

3 2