1

The following code is a minimal example of a problem I am having often in some of my documents. When compiling with lualatex with the x86-64-linux binary (in TeXLive 2013 with the latest updates) results in

!LuaTeX error (file /usr/local/texlive/2013/texmf-dist/fonts/opentype/public/lm/
lmroman10-regular.otf): Parsing CFF DICT failed. (error=-1)
 ==> Fatal error occurred, no output PDF file produced!

The error is not present when using the Windows binary.

The example code isn't very productive, but it illustrates the problem. Removing pretty much any line from this example results in proper compilation, but the problem is much harder to get rid of in my real documents which are much longer.

\documentclass{article}

\usepackage{fontspec}

\newcommand{\Item}{%
    \directlua{math.log(0,10)}%
    \begin{tabular}{l}
        1\\1\\1\\1\\1
    \end{tabular}%
    \vspace{\baselineskip}%
    \par%
}

\begin{document}

\Item
\Item
\Item
\Item
\Item
\Item
\Item
\Item
\Item

\end{document}

Is this a bug in LuaTeX or is there something inherently wrong with the example above? I would like to be able to avoid this error in the future if it is not a bug and I am causing it with something in my code that I should not do.

12
  • Shouldn't this be math.log(0.10) (period instead of comma)? Jul 20, 2013 at 17:38
  • the comma in math.log(0,10) is to make 10 the base for the logarithm, Lua returns -inf in this case Jul 20, 2013 at 17:44
  • But log(0) doesn't make sense. If the comma is an allowed syntax (I couldn't verify this) then you should use something like math.log(1,10). Jul 20, 2013 at 17:51
  • 1
    I found now the new syntax in the lua 5.2 manual. I think you should ask this on the luatex bug tracker. tracker.luatex.org Jul 20, 2013 at 18:01
  • 1
    Btw: You should add to the bug report that it is related to the log(0). (I can reproduce the problem with miktex, but not with TL13). Jul 20, 2013 at 18:19

0

Browse other questions tagged .