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: Mon, 26 Nov 2012 23:04:34 +0100 [thread overview]
Message-ID: <50B3E772.3040606@web.de> (raw)
In-Reply-To: <50B3D394.2000300@wxs.nl>
On 26/11/12 21:39, Hans Hagen wrote:
> On 11/26/2012 8:01 PM, Pablo Rodríguez wrote:
>> Sorry for the stupid question: isn't it font kerning (not kern OT table,
>> but traditional non-OT kerning) enabled when compiling this source?
>
> kerning is *always* driven by the font, given that the font has kerns
> (not all fonts need them)
Thanks for your reply, Hans.
Sorry, my question was inaccurate.
I know that kerning information is in the font, but it is ConTeXt that
uses this information (or not).
As far as I know, there are two kinds of kerningns: an OT kern feature
from the GPOS table and an old TrueType 'kern' table.
In the following sample OpenType features aren't enabled:
\usemodule[simplefonts][size=30pt]
\setmainfont[FreeSerif]
\starttext
dadedidodufafefifofufrflftlalelilolutatetitotu\par
{\em dadedidodufafefifofufrflftlalelilolutatetitotu\par}
{\bf dadedidodufafefifofufrflftlalelilolutatetitotu\par}
{\bf\em dadedidodufafefifofufrflftlalelilolutatetitotu\par}
\stoptext
I'm using TrueType fonts of FreeSerif. Isn't the TrueType 'kern' enabled
by default in ConTeXt? (The glyphs in the example above have no kerning
at all, so I wonder whether at least the TrueType 'kern' table should be
used by ConTeXt.)
Many thanks 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-26 22:04 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 [this message]
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
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=50B3E772.3040606@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).