From: Joseph Canedo <josephcanedo@gmail.com>
To: Hans Hagen <j.hagen@xs4all.nl>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Issue with missing kerns when using fallback family(or KeterYG font)
Date: Sun, 30 Dec 2018 19:05:34 +0100 [thread overview]
Message-ID: <5c2908ea.1c69fb81.419d.54eb@mx.google.com> (raw)
In-Reply-To: <b756ffba-19a0-0b5f-8e22-6982c256e60f@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1974 bytes --]
Forgot to write, thanks a lot BTW.
De : Hans Hagen
Envoyé le :dimanche 30 décembre 2018 13:18
À : mailing list for ConTeXt users; Joseph Canedo
Objet :Re: [NTG-context] Issue with missing kerns when using fallback family(or KeterYG font)
On 12/30/2018 12:06 PM, Joseph Canedo wrote:
> Dear list,
>
> Given the Following MWE, I notice that with latest beta (does not seem
> to happen before) kerns are not applied in paragraph in which there are
> some hebrew letters. This only affects text after that hebrew letters up
> to end of paragraph.
>
> I use 2 fonts in sample : EBGaramond and KeterYG (can be found in
> various places).
>
> Thanks for advising
>
> Best regards
>
> Joseph
>
> \showfontkerns
>
> \definefontfeature[base][mode=node, kern=yes, script=latn, trep=yes]
>
> \definefontfeature[hebrew][default][mode=node, lang=heb, script=hebr]
>
> \definefallbackfamily[mainfont][serif][KeterYG][preset=range:hebrew,
> scale=1.0, features=hebrew]
>
> \definefontfamily[mainfont][serif][EBGaramond][features=base]
>
> \setupbodyfont[mainfont, 9pt]
>
> \def\He{\hebrewHe}
>
> \def\Tav{\hebrewTav}
>
> \def\Vav{\hebrewVav}
>
> \starttext
>
> VA c'est {\setupalign[r2l]\Tav\He\Vav} VA c'est % there is no kern
> between latest V and A
>
> VA c'est. % kern as expected
>
> \stoptext
in font-ots.lua you can find
local lefttoright = 0
local righttoleft = 1
the second line misses a 't'
can you test with fixing that
(i'm cleaning up a bit of directional code and upcoming betas might have
more of that cleanup)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
[-- Attachment #1.2: Type: text/html, Size: 5257 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2018-12-30 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 11:06 Issue with missing kerns when using fallback family (or " Joseph Canedo
2018-12-30 12:18 ` Hans Hagen
2018-12-30 18:03 ` Issue with missing kerns when using fallback family(or " Joseph Canedo
2018-12-30 18:35 ` Hans Hagen
2018-12-30 18:43 ` Issue with missing kerns when using fallbackfamily(or " Joseph Canedo
2018-12-30 18:05 ` Joseph Canedo [this message]
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=5c2908ea.1c69fb81.419d.54eb@mx.google.com \
--to=josephcanedo@gmail.com \
--cc=j.hagen@xs4all.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).