From: "Pablo Rodríguez" <oinos@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: simple question on kerning activation
Date: Wed, 28 Nov 2012 18:17:12 +0100 [thread overview]
Message-ID: <50B64718.8070401@web.de> (raw)
In-Reply-To: <50B53A3C.7000307@wxs.nl>
On 27/11/12 23:10, Hans Hagen wrote:
>
> Normally context will automatically fall back on latn but does so by
> looking at the feature list. These fonts support so many scripts that
> it's not possible.
>
> You (pablo) can report to the font designer that for features like
> kerning a dflt,dflt pair makes sense.
Thank you very much, Hans, Wolfgang and Luigi for your help.
Sorry for the messages, but I used ConTeXt to check whether old
traditional kerning was enabled on FreeSerif fonts (not as OpenType
features). This is actually for an ereader.
As far as I know, I have to enable the Latin script in ConTeXt in all
the fonts I use with include OT features. That's fine for me.
What I couldn't understand before was that I was getting less kerns even
with the OpenType feature enabled. I took me a while to understand that
those kerns that weren't showing off in my file (my guess) were removed
in the latest version of FreeSerif.
BTW, I need to enable the Latin script even for features that belong to
other scripts, such as in Theano Didot (those contextual alternatives
and stylistic set 11 belong to the Greek script):
\usemodule[simplefonts]
\definefontfeature[default][default][script=latn,calt=yes,ss11=yes]
\setmainfont[Theano Didot]
\starttext
\startTEXpage[offset=10pt]
βάρβαροι θαυμασθεὶς
\stopTEXpage
\stoptext
Many thanks again for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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-28 17:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 19:01 Pablo Rodríguez
2012-11-26 20:39 ` Hans Hagen
2012-11-26 22:04 ` Pablo Rodríguez
2012-11-26 22:46 ` Hans Hagen
2012-11-27 16:57 ` Pablo Rodríguez
[not found] ` <50B4F2B9.4070206@wxs.nl>
2012-11-27 17:36 ` Pablo Rodríguez
2012-11-27 17:42 ` luigi scarso
2012-11-27 17:46 ` Pablo Rodríguez
2012-11-27 17:49 ` luigi scarso
2012-11-27 17:56 ` Hans Hagen
2012-11-27 19:34 ` Pablo Rodríguez
2012-11-27 21:34 ` Wolfgang Schuster
2012-11-27 21:43 ` Pablo Rodríguez
2012-11-27 21:58 ` Wolfgang Schuster
2012-11-27 22:10 ` Hans Hagen
2012-11-28 17:17 ` Pablo Rodríguez [this message]
2012-11-27 21:39 ` Hans Hagen
2012-11-27 21:48 ` Hans Hagen
2012-11-26 23:11 ` Wolfgang Schuster
2012-11-27 16:59 ` Pablo Rodríguez
2012-11-27 17:11 ` luigi scarso
2012-11-28 9:01 ` Hans Hagen
2012-11-28 9:13 ` Wolfgang Schuster
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=50B64718.8070401@web.de \
--to=oinos@web.de \
--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).