From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: 'kern': TrueType table and GPOS lookup feature
Date: Sun, 2 Dec 2012 15:12:04 +0200 [thread overview]
Message-ID: <20121202131204.GA15717@khaled-laptop> (raw)
In-Reply-To: <CAEmWKkR1DVU6tBE9GvEJiSMDJNc2E+TX_+Jx7VPGemMBqM8N6w@mail.gmail.com>
On Sun, Dec 02, 2012 at 10:58:56AM +0100, Steve White wrote:
> Hi all,
>
> I finally got something like Pablo's test working on my system. It doesn't
> show much new. As had already been established, with the right ConTeXt
> switches, OpenType features of kerning and ligatures work correctly with
> FreeSerif.
>
> Find attached. If there's a better way to do this, please comment: I may
> put some of this in the FreeFront usage notes. (Hm... I may tighten the
> italic y a bit.)
>
> A question remains: Why does ConTeXt (like some other TeX derivatives that
> use OpenType) not determine the OpenType script of runs of text from the
> Unicode (or other encoding) character range? All other font layout systems
> I know of do this. (Remember- a run of text in the OpenType sense is not
> the same as the scope of a TeX environment, it is typically a word,
> separated by white space or punctuation.)
Determining the script of a run of text is not that simple, take
"english (ARABIC.)"; to which script should the parenthesis and the
period be classified? (they have a "common" script property in Unicode
and not assigned to any given script). Unicode annex #24 provides an
algorithm for to handle this that an engine should implement:
http://www.unicode.org/reports/tr24/
Regards,
Khaled
___________________________________________________________________________________
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-12-02 13:12 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 [this message]
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
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=20121202131204.GA15717@khaled-laptop \
--to=khaledhosny@eglug.org \
--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).