ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Pablo Rodríguez" <oinos@web.de>
Subject: Re: simple question on kerning activation
Date: Mon, 26 Nov 2012 21:39:48 +0100	[thread overview]
Message-ID: <50B3D394.2000300@wxs.nl> (raw)
In-Reply-To: <50B3BC7C.8000401@web.de>

On 11/26/2012 8:01 PM, Pablo Rodríguez wrote:
> Hi there,
>
> I have the following file to check a feature in FreeSerif:
>
> \setuppapersize[A4,landscape]
> \usemodule[simplefonts][size=30pt]
> \setmainfont[FreeSerif]
> \starttext
>
> dadedidodufafefifofufrflftlalelilolutatetitotu\par
> {\em dadedidodufafefifofufrflftlalelilolutatetitotu\par}
> {\bf dadedidodufafefifofufrflftlalelilolutatetitotu\par}
> {\bf\em dadedidodufafefifofufrflftlalelilolutatetitotu\par}
> \stoptext
>
> 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)

you can see kern sin action with:

\starttext

     \showfontkerns \input ward

\stoptext


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
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2012-11-26 20:39 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 [this message]
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
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=50B3D394.2000300@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=oinos@web.de \
    /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).