From: Hans Hagen <j.hagen@xs4all.nl>
To: Joseph <josephcanedo@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bidi + protrusion issue in LMTX
Date: Tue, 3 Mar 2020 10:09:52 +0100 [thread overview]
Message-ID: <1288e0c5-f5c6-8a29-c211-e133588faaa2@xs4all.nl> (raw)
In-Reply-To: <5e5d5ece.1c69fb81.787b8.5571@mx.google.com>
On 3/2/2020 8:30 PM, Joseph wrote:
> Hi,
>
> I found that in some cases bidi text seems to inhibit protrusion feature
> in text typesetting in LMTX (works fine with luatex 1.10).
>
> MWE below (difference is in first paragraph, second is for comparison
> and is same in both):
>
> \language[fr]
>
> \mainlanguage[fr]
>
> \definefontfamily[mainfont][serif][EBGaramond][features={protrusion=quality,
> expansion=quality}]
you best can do this if you also want kerns:
\definefontfeature[mydefault][default][protrusion=quality,expansion=quality]
\definefontfamily[mainfont][serif][EBGaramond][features=mydefault]
anyway, i'll look at it
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
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2020-03-03 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 19:30 Joseph
2020-03-03 9:09 ` Hans Hagen [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=1288e0c5-f5c6-8a29-c211-e133588faaa2@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).