Re: [Dev-luatex] Some legacy fonts cause "invalid list tail, probably missing glue"

19 Feb 2020

      On Wed, Feb 19, 2020 at 9:55 AM Marcel Fabian Krüger 
wrote:
...
On Tue, Feb 18, 2020 at 11:44:37PM +0100, luigi scarso wrote:
...
On Tue, Feb 18, 2020 at 12:54 PM Marcel Fabian Krüger 
wrote:
...
A plain LuaTeX example for this would be
\directlua{
  callback.register('kerning', node.kerning)
font.current(font.define {
    name = "dummy",
    type = "virtual",
    characters = {
      {
        width = 655360,
        height = 655360,
        depth = 655360,
        commands = {},
      },
      right_boundary = {
        width = 655360,
        height = 655360,
        depth = 655360,
      },
    },
  })
}
\char1
\bye
this fails with
(see the transcript file for additional
information)
! error:  (file dummy) (type 3): font dummy at 72 not found
--
luigi
Right, I forgot that LuaTeX is not particularly happy about empty
commandds tables. But after replacing
commands = {}
by
commands = {{"right", 0}}
and adding some f.fonts table the not found error disappears. But I am
surprised that it even got that far for you: On my system (vanilla
TeXLive 2019 on (Arch) Linux, both with the regular LuaTeX 1.10 and the
current head of "experimental") the actual issue "invalid list tail,
probably missing glue" appears long before LuaTeX reaches the font
embedding stage.
not surprise, could be that I am testing a local version  not yet pushed.
For this reason is better to have a minimal and complete example, otherwise
we waste time .

With my local version
\directlua{
  callback.register('kerning', node.kerning)
  font.current(font.define{
    name = "dummy",
    type = "virtual",
    characters = {
      {
        width = 655360,
        height = 655360,
        depth = 655360,
        commands = {{"right", 0}},
      },
      right_boundary = {
        width = 655360,
        height = 655360,
        depth = 655360,
      },
    },
  })
}
\char1
\bye

$ luatex --fmt=luatex-plain test-tail.tex
doesn't complain .

-- 
luigi