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 17:05:27 +0100 [thread overview]
Message-ID: <50B8D947.50003@wxs.nl> (raw)
In-Reply-To: <CAEmWKkSCxJ8LVmNwrb-Nq2GcuQacDptgxQUWfrsent+Fwq8V8A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2925 bytes --]
On 11/30/2012 10:58 AM, Steve White wrote:
> 2) I understood that ConTeXt only uses the old-style TrueType 'kern'
> table, rather than the OpenType 'kern' GPOS lookup. If that is the
> case, I would suggest that you consider to change the logic to first
> use the OpenType lookup, and if it doesn't exist, fall back to the
> TrueType table. Several applications are already complaining that both
> exist; the plan is to drop support for the TrueType table in FreeFont.
I has always supported both but the user does not show the difference.
> 3) In most applications, the script of a run of text is determined from
> the Unicode. This is the assumption made in FreeFont. The GNU FreeFont
> policy starts from its essence as a Unicode font, in which no particular
> script is default. (Some generic features that are not specific to any
> script, are in {dflt,dflt}.)
>
> 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?
because one text can contain multiple scripts
> It appears that there maybe some conflict her with TeX implementaions.
> I don't completely understand this. Maybe we can find a solution.
If you have context installed and running, you can do this:
\usemodule[fnt-20,art-01]
\starttext
\definefontfeature
[freeserif-default]
[default]
[script=latn]
\setvariables
[otftracker]
[font=file:freeserif.ttf,
size=24pt,
figure=,
features=freeserif-default,
title=Feature Check,
sample={dadedidodufafefifofufrflftlale}]
\setvariables
[otftracker]
[font=file:freeserif.ttf,
size=24pt,
figure=,
features=freeserif-default,
title=Feature Check,
sample={lilolutatetitotu}]
\stoptext
This gives insight in the stepwise processing of features (something
that is handy for relatively complex fonts, for instance those dealign
with arabic).
> 4) I have written something like Pablo's test using XeTeX and fontspec.
> Kerning works very well with GNU FreeFont. Find attached.
maybe xetex defaults to latn
> 5) There was also a report that OpenType kerning doesn't work in some
> E-Book readers (I know this isn't the forum for that, but ...) . My
> iriver Story kerns very nicely text in FreeSerif. Can I get an example
> of an E-reader for which kerning fails? (I really don't doubt that they
> exist!)
Natively I suppose? If a pdf file is viewed on an ebook reader it's not
the ereader's issue.
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
-----------------------------------------------------------------
[-- Attachment #2: freefont.pdf --]
[-- Type: application/pdf, Size: 54377 bytes --]
[-- Attachment #3: freefont.tex --]
[-- Type: text/plain, Size: 471 bytes --]
\usemodule[fnt-20,art-01]
\starttext
\definefontfeature
[freeserif-default]
[default]
[script=latn]
\setvariables
[otftracker]
[font=file:freeserif.ttf,
size=24pt,
figure=,
features=freeserif-default,
title=Feature Check,
sample={dadedidodufafefifofufrflftlale}]
\setvariables
[otftracker]
[font=file:freeserif.ttf,
size=24pt,
figure=,
features=freeserif-default,
title=Feature Check,
sample={lilolutatetitotu}]
\stoptext
[-- 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-11-30 16:05 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
2012-11-30 16:05 ` Hans Hagen [this message]
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=50B8D947.50003@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).