From: Georg Duffner <g.duffner@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: font trickery
Date: Wed, 15 May 2013 08:09:22 +0200 [thread overview]
Message-ID: <51932692.8020800@gmail.com> (raw)
In-Reply-To: <op.ww3i22w4pw6hmh@ishamid-pc>
Am 15.05.2013 00:51, schrieb Idris Samawi Hamid ادريس سماوي حامد:
> Hi Hans,
>
> On Tue, 14 May 2013 12:01:36 -0600, Hans Hagen <pragma@wxs.nl> wrote:
>
>> I'm on-and-off working on the more technical font manual and in the
>> process also check some old code i've laying around (deciding on what
>> to include and not). I'm also revising the tracer styles.
>>
>> Which makes me wonder: are there specific additional features that one
>> would like to see in context (mkiv only of course) with respect to
>> font support?
>
> This may be beyond the scope of your current plans, but worth
> considering: It would be nice to have a mechanism where we can
> override/add opentype gsub and gpos features. Early on in the history of
> luatex we once had a mechanism that did this using FontForge's version
> of Adobe Feature Files. From what I understand, the AFF syntax is
> finally mature and supports all lookup types:
>
> http://www.adobe.com/devnet/opentype/afdko/topic_feature_file_syntax.html
>
> Or maybe we have our own syntax in lua, goodies etc. Anyway, a way to
> control/override opentype gsub and gpos behavior would be interesting.
> Even if a total controller is too ambitious/unwieldy, just being able to
> do a few basic gsub/gpos tricks may be useful for, e.g., bugs in the font.
>
> Anyway, something to think about.
>
> Best wishes
> Idris
Hi Idris and Hans,
this is a great idea. Is this not available any longer in current
luatex? The fontspec (xelatex+lualatex) manual lists this as a luatex
only feature (I’ve used it once some time ago). I know a lot of fonts
and other problems that could be fixed this way. I’d prefer to stay with
the AFF syntax which is well established.
Best regards,
Georg
___________________________________________________________________________________
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:[~2013-05-15 6:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 18:01 Hans Hagen
2013-05-14 22:51 ` Idris Samawi Hamid ادريس سماوي حامد
2013-05-15 6:09 ` Georg Duffner [this message]
2013-05-15 14:51 ` Idris Samawi Hamid ادريس سماوي حامد
2013-05-15 16:41 ` Khaled Hosny
2013-05-17 23:55 ` Hans Hagen
2013-05-18 0:19 ` Idris Samawi Hamid ادريس سماوي حامد
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=51932692.8020800@gmail.com \
--to=g.duffner@gmail.com \
--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).