On 23-2-2011 6:05, Ulrike Fischer wrote:
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, ...).
There will be some documentation once it is stable enough. I
Am Tue, 22 Feb 2011 18:05:58 +0100 schrieb Hans Hagen:
Khaled had another idea to manipulate (reencode) fonts: He suggested
to put a function in fonts.trigger. (Example below). I have some
questions regarding this example:
1. Is there a basic flaw in the idea?
When triggers are done,
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
Hello,
Khaled had another idea to manipulate (reencode) fonts: He suggested
to put a function in fonts.trigger. (Example below). I have some
questions regarding this example:
1. Is there a basic flaw in the idea?
2. Is the interface more or less stable or will it probably change
in the future?
On 22-2-2011 4:22, Ulrike Fischer wrote:
Hello,
Khaled had another idea to manipulate (reencode) fonts: He suggested
to put a function in fonts.trigger. (Example below). I have some
questions regarding this example:
1. Is there a basic flaw in the idea?
When triggers are done, there are only
On 22-2-2011 4:22, Ulrike Fischer wrote:
Hello,
Khaled had another idea to manipulate (reencode) fonts: He suggested
to put a function in fonts.trigger. (Example below). I have some
questions regarding this example:
I'll add the following to the luatex-fonts code. It demonstrates how to
use
