ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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 17:36:35 +0100	[thread overview]
Message-ID: <20130329163635.GB15331@phlegethon> (raw)
In-Reply-To: <5155BD77.6060305@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1306 bytes --]

···<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.

> >Compared to Plain, Context adds a lot to the “.parameters” table.
> >Sadly, writing to it doesn’t appear to change anything …
> 
> well, why would you .. the font is already passed to tex and you
> cannot change that frozen state (imagine: what would a change in
> width of a char mean halfway? it woul dnot work well with the
> backend) ... what would you like to change?

That wasn’t 100% serious. Just me experimenting.

Best
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
___________________________________________________________________________________

  reply	other threads:[~2013-03-29 16:36 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 [this message]
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=20130329163635.GB15331@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).