From: Hans Hagen <pragma@wxs.nl>
To: ConTeXt ML <ntg-context@ntg.nl>
Subject: Re: error calling font.getfont() on certain fonts
Date: Fri, 29 Mar 2013 15:21:04 +0100 [thread overview]
Message-ID: <5155A350.4040401@wxs.nl> (raw)
In-Reply-To: <20130328174101.GA4456@phlegethon>
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
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.)
> Best regards
> Philipp
>
>
> %% working fonts:
> %\setupbodyfont[iwona]
> %\setupbodyfont[computer-modern-unicode]
> %\setupbodyfont[antykwa-poltawskiego]
> %% ... ?
>
> %% not working:
> \setupbodyfont[modern]
> %\setupbodyfont[antykwa]
> %\setupbodyfont[termes]
> %\setupbodyfont[pagella]
> %\setupbodyfont[bonum]
> %% ... ?
>
> \starttext
> foo
> \ctxlua{font.getfont( font.current() )}
> bar
> \stoptext
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
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-03-29 14:21 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 [this message]
2013-03-29 15:29 ` Philipp Gesang
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=5155A350.4040401@wxs.nl \
--to=pragma@wxs.nl \
--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).