Re: [NTG-context] error calling font.getfont() on certain fonts

2013-03-29 Thread 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

Re: [NTG-context] error calling font.getfont() on certain fonts

2013-03-29 Thread Philipp Gesang
···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

Re: [NTG-context] error calling font.getfont() on certain fonts

2013-03-29 Thread Hans Hagen
On 3/29/2013 4:29 PM, Philipp Gesang wrote: 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

Re: [NTG-context] error calling font.getfont() on certain fonts

2013-03-29 Thread Philipp Gesang
···date: 2013-03-29, Friday···from: Hans Hagen··· On 3/29/2013 4:29 PM, Philipp Gesang wrote: 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

Re: [NTG-context] error calling font.getfont() on certain fonts

2013-03-29 Thread Hans Hagen
On 3/29/2013 5:36 PM, Philipp Gesang wrote: ···date: 2013-03-29, Friday···from: Hans Hagen··· On 3/29/2013 4:29 PM, Philipp Gesang wrote: 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