ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Joseph <josephcanedo@gmail.com>
Subject: Re: Missing kern when using \feature
Date: Fri, 8 Jan 2021 16:32:06 +0100	[thread overview]
Message-ID: <4a1a7754-8497-9baa-ecf8-2c306c8b74bb@xs4all.nl> (raw)
In-Reply-To: <22AFB975-8F6D-47AD-8469-08296EA5CE9F@hxcore.ol>

On 1/8/2021 2:45 PM, Joseph wrote:
> Dear list,
> 
> Still spot a minor difference with previous LMTX versions. MWE 
> reproduces it (in previous beta we had twice as kerning, now it’s no 
> kerning at all).
> 
> Thanks a lot as usual.
> 
> \definefontfeature[xvicentury][mode=node]
> 
> \definefontfeature[default][default][kern=yes]
> 
> \definefontfamily[mainfont][serif][EBGaramond]
> 
> \setupbodyfont[mainfont, 9pt]
> 
> \showfontkerns
> 
> \starttext
> 
> Chapitre {\feature[-][xvicentury]v}. % no kerning between v and .

indeed there should be no kerning because there are two different font 
setups (lmtx is a bit better in these dynamic features: more strict 
testing at the cost of a bit more runtimen but optimized so not noticeable)

> Chapitre v.

i see a kern here

> \stoptext
> 
> 
> ___________________________________________________________________________________
> 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://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
> 


-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2021-01-08 15:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 13:45 Joseph
2021-01-08 15:32 ` Hans Hagen [this message]
2021-01-08 15:41   ` RE : " Joseph

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=4a1a7754-8497-9baa-ecf8-2c306c8b74bb@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=josephcanedo@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).