ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: error calling font.getfont() on certain fonts
Date: Fri, 29 Mar 2013 17:42:07 +0100	[thread overview]
Message-ID: <5155C45F.2070907@wxs.nl> (raw)
In-Reply-To: <20130329163635.GB15331@phlegethon>

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 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).
>>
>> even then it's of not much use for context as we have more data and
>> keep that data at the lua end so font.getfont has no benefits then
>
> For my purpose the benefit is that I can access some info about
> the font with the same code in all three formats.

ok, *.parameters probably carries the same info but for the rest you 
cannot assume that the context font handler (plus the derived generic 
one) will limit itself to that subset; in a similar fashion there is a 
difference between what context keeps track of and stores and the raw 
loaded otf font data

(in other words: cross macro package has a limited meaning)

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
___________________________________________________________________________________


      reply	other threads:[~2013-03-29 16:42 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
2013-03-29 16:12     ` Hans Hagen
2013-03-29 16:36       ` Philipp Gesang
2013-03-29 16:42         ` Hans Hagen [this message]

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=5155C45F.2070907@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).