From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Palatino patch for the current ConTeXt version
Date: Sun, 17 Nov 2013 12:44:30 +0100 [thread overview]
Message-ID: <5288AC1E.6040406@wxs.nl> (raw)
In-Reply-To: <001a01cee387$691cd370$3b567a50$@tosovsky@email.cz>
On 11/17/2013 12:23 PM, honyk wrote:
> Hello Everyone,
>
> I am trying to fix a Palatino small caps issue using the procedure explained
> here:
> http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV
>
> That fix seems to be obsolete nowadays and returning errors.
>
> I've changed
> fonts.otf.enhancers.patches["^pala"]
> to
> fonts.handlers.otf.enhancers.patches["^pala"]
> which compiles, but it does nothing.
>
> I've also tried this variant, but that 'patch' function is never called even
> though I clear my font cache every run:
>
> \startluacode
> local fonts = fonts
> local otf = fonts.handlers.otf
> local patches = otf.enhancers.patches
> local register = patches.register
> local report = patches.report
>
> function patch (data,filename)
> report("I am here")
> report("processing data %s", table.serialize(data))
> end
>
> register("after","prepare glyphs","^pala", patch)
> \stopluacode
>
>
> Any idea?
patches are applied when a font is cached so you need to wipe the cache
after defining such a patch
there are several ways to apply patches runtime, see *.lfg files (and
also fonts-mkiv.pdf)
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 parent reply other threads:[~2013-11-17 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a01cee387$691cd370$3b567a50$@tosovsky@email.cz>
2013-11-17 11:44 ` Hans Hagen [this message]
2013-11-26 23:40 ` Jan Tosovsky
[not found] ` <008801ceeb00$db41e820$91c5b860$@tosovsky@email.cz>
2013-11-27 8:37 ` Hans Hagen
2013-11-27 20:16 ` Jan Tosovsky
[not found] ` <00b901ceebad$900fb0a0$b02f11e0$@tosovsky@email.cz>
2013-11-27 20:55 ` Hans Hagen
2013-11-29 19:44 ` Jan Tosovsky
2013-12-01 8:40 ` Jan Tosovsky
2013-12-21 10:02 ` Jan Tosovsky
2013-11-17 11:23 honyk
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=5288AC1E.6040406@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).