r1551 | taco | 2008-10-08 17:53:52 +0200 (Wed, 08 Oct 2008) | 2 lines
Changed paths:
M /trunk/src/texk/web2c/luatexdir/lang/texlang.c
possibly fix an access violation on win32
-
r1548 | taco | 2008-10-08 12:30:25 +0200 (Wed, 08 Oct 2008) | 2 lines
Changed paths:
M /trunk/src/texk/web2c/luatexdir/tex/textoken.c
fix handling of active csname ^^00
---
Hi Ulrike,
Ulrike Fischer wrote:
>
> \documentclass{article}
> \begin{document}
> \catcode`\^^00=13
> \ifnum`^^00=0 ja \else nein \fi
>
> \end{document}
>
> When processed with LaTeX or XeLaTeX I get a document with "ja".
> Luatex gives "nein". Is this difference to be expected?
No, you found
r1546 | taco | 2008-10-08 09:54:08 +0200 (Wed, 08 Oct 2008) | 2 lines
Changed paths:
M /trunk/src/texk/web2c/luatexdir/lua/luatoken.c
don't duplicate #'s in \directlua
-
Hello,
> > So with \luaescapestring, the `#' is not doubled anymore, without it
> > still is. Although most of the time, strings will be passed to Lua
> > through \luaescapestring, this behaviour still creates problems when
> > `#' is used inside Lua code (as in the commented line A above, where
Hello,
I ran into a problem with the LaTeX-package listing related to the
handling of extendedchars (it can be easily avoid by using
extendedchars=false).
I think I have tracked down the problem to the following difference
between luatex and pdftex/xetex:
\documentclass{article}
\begin{documen
Jonathan Sauer wrote:
>
> So with \luaescapestring, the `#' is not doubled anymore, without it
> still is. Although most of the time, strings will be passed to Lua
> through \luaescapestring, this behaviour still creates problems when
> `#' is used inside Lua code (as in the commented line A abo
Hello,
> Actually the problem was with \luaescapestring. Commit #1544 changes
> the behaviour of \luaescapestring so that it no longer duplicates
> characters with catcode 6. Please verify that that does what you want.
Thank you very much! I tried it with the following (simpler) example:
%&luat
