ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: news3@nililand.de, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: generic font loader + luaotfload: 'nodepool' (a nil value)"
Date: Fri, 14 Jul 2017 19:20:38 +0200	[thread overview]
Message-ID: <de036426-ed31-3f32-0280-9faa7146203a@wxs.nl> (raw)
In-Reply-To: <z6luvn37lvnm$.dlg@nililand.de>

On 7/14/2017 4:39 PM, Ulrike Fischer wrote:
> I have been trying to use the newest generic font loader
> (luatex-fonts-merged.lua) in the context minimals with luaotfload
> in latex.
> 
> This mostly worked with one exception: luaotfload-letterspace.lua
> reference a value that no longer exists:
> 
> "...mf-dist/tex/luatex/luaotfload/luaotfload-letterspace.lua:73:
> attempt to index local 'nodepool' (a nil value)".
> 
> luaotfload does
> 
> local nodedirect         = nodes.nuts
> local nodepool           = nodedirect.pool
> local new_kern           = nodepool.kern
> 
> and uses new_kern here
> 
> local kern_injector = function (fillup, kern)
>    if fillup then
>      local g = new_glue(kern)
>      local s = getfield(g, "spec")
>      setfield(s, "stretch", kern)
>      setfield(s, "stretch_order", 1)
>      return g
>    end
>    return new_kern(kern)
> end

yes, i decided to limit the dependencies ... (also because the kern 
allocator was a plug outside context)

you can use:

   local new = node.direct.new

   local g = new("glue")
   setfield(g, "stretch", kern)
   setfield(g, "stretch_order", 1)

and forget about the spec subnode which is gone for a while now (but 
still faked)

> The error goes away when I add this to the fontloader (from an older
> version):
> 
> nuts.new=direct.new
> -- new UF
>     nuts.pool={}
>     function nuts.pool.kern(k)
>     local n=nuts.new("kern",1)
>     setfield(n,"kern",k)
>     return n
>     end
> -- end UF
> nuts.getprop=nuts.getattr
> 
> But I would prefer to change luaotfload-letterspace.lua to use
> whatever should be used to get the correct effect. Can someone tell
> me how to do it??
> 
> 
> 


-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2017-07-14 17:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 14:39 Ulrike Fischer
2017-07-14 17:20 ` Hans Hagen [this message]
2017-07-14 18:26   ` Ulrike Fischer
2017-07-14 18:56     ` Hans Hagen
2017-07-14 22:56       ` Ulrike Fischer
2017-07-15  7:50         ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=de036426-ed31-3f32-0280-9faa7146203a@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=news3@nililand.de \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).