From: Steve White <stevan.white@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: 'kern': TrueType table and GPOS lookup feature
Date: Sun, 2 Dec 2012 10:58:56 +0100 [thread overview]
Message-ID: <CAEmWKkR1DVU6tBE9GvEJiSMDJNc2E+TX_+Jx7VPGemMBqM8N6w@mail.gmail.com> (raw)
In-Reply-To: <CAG5iGsA4O_5wkB2A=t9S6PKWSV3bac+t-63VVqnt1T_UZMZcwg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1388 bytes --]
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.)
Maybe there is some rationale, but I haven't heard it yet.
Let me propose a different interpretation for the existing 'script' setting
as used in the \definefontfeature command in the attached tex file:
* If it is not present, the engine would revert to using the script
indicated by the encoding for each run of text.
* If it is present, it would mean "activate only features that match the
specified script".
It appears to me this would not change the rendering of many documents, if
any, but it would alleviate the confusion that gave rise to this thread.
Cheers!
[-- Attachment #1.2: Type: text/html, Size: 1490 bytes --]
[-- Attachment #2: context-kern5.pdf --]
[-- Type: application/pdf, Size: 14304 bytes --]
[-- Attachment #3: context-kern5.tex --]
[-- Type: application/x-tex, Size: 449 bytes --]
[-- Attachment #4: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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 9:58 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 [this message]
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
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=CAEmWKkR1DVU6tBE9GvEJiSMDJNc2E+TX_+Jx7VPGemMBqM8N6w@mail.gmail.com \
--to=stevan.white@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).