From: Philipp Gesang <Philipp.Gesang@alumni.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: error calling font.getfont() on certain fonts
Date: Fri, 29 Mar 2013 16:29:15 +0100 [thread overview]
Message-ID: <20130329152851.GA15331@phlegethon> (raw)
In-Reply-To: <5155A350.4040401@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2189 bytes --]
···<date: 2013-03-29, Friday>···<from: Hans Hagen>···
> On 3/28/2013 6:41 PM, Philipp Gesang wrote:
> >Hi all,
> >
> >I get an error when I run this code:
> >
> > \ctxlua{font.getfont( font.current() )}
> >
> >(Complete example below.) Oddly, whether or not this fails
> >depends on the font. The issue does occur with both today’s beta
> >and Tex Live. The error message is
> >
> > error: .../context/tex/texmf-context/tex/context/base/node-inj.lua:97: attempt to perform arithmetic on local 'factor' (a nil value)
> >
> >At the same time, in Plain the equivalent code works fine for all
> >fonts. Bug or feature?
>
> it's a side effect ... it looks like font.getfont operates on the
> table passed to tex and when you request it it probably fills in
> some data (like parameters) thereby overloading / wiping out
> existing stuff so after that call the data structure as context uses
> (and needs) it is messed up
I just read that in the manual:
Note that at the moment, each access to the font.fonts or call
to font.getfont creates a lua table for the whole font. This
process can be quite slow. In a later version of LuaTEX, this
interface will change (it will start using userdata objects
instead of actual tables).
> add this after the definition of
> definers.read(specification,size,id) and it will probably work ok
>
> function font.getfont(id)
> return fontdata[id] -- otherwise issues
> end
>
> (I'll add a similar overload someplace else.)
Great! Looking forward to the next update.
> in context you can try this:
>
> \startluacode
> function font.getfont(id)
> return fonts.hashes.identifiers[id]
> end
> \stopluacode
>
> \starttext
>
> foo
> \ctxlua{inspect(font.getfont( font.current()).parameters )}
> bar
> \stoptext
>
> if you comment the function overload you see the difference
Compared to Plain, Context adds a lot to the “.parameters” table.
Sadly, writing to it doesn’t appear to change anything …
Philipp
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-03-29 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 17:41 Philipp Gesang
2013-03-29 14:21 ` Hans Hagen
2013-03-29 15:29 ` Philipp Gesang [this message]
2013-03-29 16:12 ` Hans Hagen
2013-03-29 16:36 ` Philipp Gesang
2013-03-29 16:42 ` 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=20130329152851.GA15331@phlegethon \
--to=philipp.gesang@alumni.uni-heidelberg.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).