From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: 'kern': TrueType table and GPOS lookup feature
Date: Fri, 30 Nov 2012 16:41:24 +0100 [thread overview]
Message-ID: <50B8D3A4.8050809@wxs.nl> (raw)
In-Reply-To: <20121130141313.GD24572@khaled-laptop>
On 11/30/2012 3:13 PM, Khaled Hosny wrote:
> On Fri, Nov 30, 2012 at 10:58:25AM +0100, Steve White wrote:
>> There was a suggestion that Latin kerns should be activated by
>> {script,lang}={dflt,dflt}. Let me ask, should Devanagari kerns also be
>> activated by {dflt, dflt}? If not, why?
>
> My own policy is, unless a feature must be restricted to a specific
> script/language (e.g. a locale-specific feature), all features should be
> assigned to *all* scripts in the font, including DFLT/dflt, because
> there is technical reason for doing otherwise and it would help
> applications not doing automatic script/language itemisation (both
> OpenType-enabled TeX engines, for example).
That makes much sense (unless a font has hundreds of different lookups
for multiple features which could slow down basic processing).
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:[~2012-11-30 15:41 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 7:06 Pablo Rodríguez
2012-11-30 9:13 ` Hans Hagen
2012-11-30 9:58 ` Steve White
2012-11-30 10:18 ` luigi scarso
2012-11-30 11:40 ` Steve White
2012-11-30 12:24 ` luigi scarso
2012-11-30 14:25 ` Steve White
2012-11-30 15:30 ` luigi scarso
2012-11-30 15:38 ` Hans Hagen
2012-11-30 18:12 ` Steve White
2012-11-30 18:22 ` Hans Hagen
2012-11-30 19:37 ` luigi scarso
2012-11-30 21:25 ` Steve White
2012-11-30 22:02 ` Hans Hagen
2012-11-30 23:57 ` Pablo Rodríguez
2012-12-01 16:22 ` Steve White
2012-12-01 19:22 ` luigi scarso
2012-12-01 19:38 ` Aditya Mahajan
2012-12-01 19:46 ` luigi scarso
2012-12-01 19:58 ` Aditya Mahajan
2012-12-01 21:09 ` luigi scarso
2012-12-02 9:58 ` Steve White
2012-12-02 13:12 ` Khaled Hosny
2012-12-02 14:32 ` Steve White
2012-12-02 14:49 ` Khaled Hosny
2012-12-02 10:10 ` Steve White
2012-12-02 10:24 ` luigi scarso
2012-12-02 10:43 ` Wolfgang Schuster
2012-12-02 11:08 ` Steve White
2012-12-02 11:48 ` luigi scarso
2012-11-30 15:43 ` Hans Hagen
2012-11-30 14:13 ` Khaled Hosny
2012-11-30 15:41 ` Hans Hagen [this message]
2012-11-30 16:05 ` Hans Hagen
2012-11-30 16:39 ` Bill Meahan
2012-11-30 18:08 ` Steve White
2012-11-30 19:07 ` Bill Meahan
2012-11-30 21:24 ` Steve White
2012-11-30 18:34 ` Steve White
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=50B8D3A4.8050809@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).