From: Hans Hagen <pragma@wxs.nl>
To: news3@nililand.de, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: manipulate ttf-fonts loaded with luatex
Date: Thu, 28 Oct 2010 19:17:19 +0200 [thread overview]
Message-ID: <4CC9B01F.1060907@wxs.nl> (raw)
In-Reply-To: <1bnkh4sd7r41c$.dlg@nililand.de>
On 28-10-2010 7:08, Ulrike Fischer wrote:
> Am Thu, 28 Oct 2010 18:01:07 +0200 schrieb Hans Hagen:
>
>
>>> The question I have: How can I correct the fontdata after I have
>>> loaded the font?
>>
>> in context it is possible to 'patch' a font before it gets cached but
>> that's just a hack; in luaotf I can imagine that you intercept the font
>> just before it gets passed to tex, but anyway, it's asking for problems
>> with respect to future proof processing
>
> Well I don't want to patch the font system. But why can't I change
> the font data after the \font\test=... line? Is the data somewhere
> in the memory where it can't be touched? If yes is it possible to
> copy the data, change it and then use the changed data to define a
> new font \testb?
as direct manipulation at that level is doomed to fail in the future
(nothing is written in stone till we have luatex 1.0) the best I can
think of is to provide a function that does the job i.e. stupify the
mapping, something fonts.otf.simplifynamemapping or so, or better
provide that as feature so that one can enable it; really this is the
only robust way
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:[~2010-10-28 17:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 10:37 Ulrike Fischer
2010-10-27 18:35 ` Aditya Mahajan
2010-10-27 20:01 ` Ulrike Fischer
2010-10-27 21:32 ` Aditya Mahajan
2010-10-28 8:34 ` Ulrike Fischer
2010-10-28 12:33 ` Hans Hagen
2010-10-28 12:57 ` Ulrike Fischer
2010-10-28 13:08 ` Taco Hoekwater
2010-10-28 13:29 ` Ulrike Fischer
2010-10-28 13:33 ` Khaled Hosny
2010-10-28 14:59 ` Hans Hagen
2010-10-28 15:37 ` Ulrike Fischer
2010-10-28 16:01 ` Hans Hagen
2010-10-28 17:08 ` Ulrike Fischer
2010-10-28 17:17 ` Hans Hagen [this message]
2010-10-28 17:48 ` Ulrike Fischer
2010-10-28 18:56 ` Hans Hagen
2010-11-02 15:16 ` Ulrike Fischer
2010-11-02 15:40 ` Hans Hagen
2010-10-28 19:35 ` Hans Hagen
2010-10-28 19:46 ` Khaled Hosny
2010-10-28 20:29 ` Hans Hagen
2010-10-28 15:48 ` Taco Hoekwater
2010-10-28 15:59 ` Khaled Hosny
2010-10-28 16:06 ` Hans Hagen
2010-10-28 16:29 ` Hans Hagen
2010-10-28 16:47 ` Ulrike Fischer
2010-10-28 17:03 ` taco
2010-10-28 19:48 ` Khaled Hosny
2010-10-28 13:10 ` Hans Hagen
2010-10-28 13:34 ` Ulrike Fischer
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=4CC9B01F.1060907@wxs.nl \
--to=pragma@wxs.nl \
--cc=news3@nililand.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).