From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: reencode fonts with fonts.trigger
Date: Wed, 23 Feb 2011 18:05:53 +0100 [thread overview]
Message-ID: <7mukxy5locqn$.dlg@nililand.de> (raw)
In-Reply-To: <4D640EAC.7080203@wxs.nl>
Am Tue, 22 Feb 2011 20:29:48 +0100 schrieb Hans Hagen:
> I'll add the following to the luatex-fonts code. It demonstrates how to
> use postprocessing hooks. (It should work with the current code, unless
> you define multiple mapping of the same font, for which i've added a
> patch).
The code didn't work with the context in miktex and a context from a
minimals about 3 month old (I got no errors but no reencoding
either). It worked fine with a current context.
In latex/luaotfload I got at first an error ("enc" is nil). After I
added "if not fonts.enc then fonts.enc = { } end" it compiled but
didn't reencode. So I guess I will have to wait until luaotfload
gets updated before I can use this solution (which looks fine).
But I wished they were some documentation about the general
structure of the font loading and processing and all this fields
(fonts.manipulators, fonts.triggers, tfmdata.postprocessors, ...).
Is there someone (beside yourself) who still understand the overall
picture?
--
Ulrike Fischer
___________________________________________________________________________________
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:[~2011-02-23 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 15:22 Ulrike Fischer
2011-02-22 17:05 ` Hans Hagen
2011-02-23 16:46 ` Ulrike Fischer
2011-02-22 19:29 ` Hans Hagen
2011-02-23 17:05 ` Ulrike Fischer [this message]
2011-02-25 12:30 ` 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='7mukxy5locqn$.dlg@nililand.de' \
--to=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).