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>,
	"Jairo A. del Rio" <jairoadelrio6@gmail.com>
Subject: Re: Some ligatures don't work in latest LMTX
Date: Thu, 7 Jan 2021 16:20:03 +0100	[thread overview]
Message-ID: <24267899-2000-b5a7-8f8e-5cc247998bad@xs4all.nl> (raw)
In-Reply-To: <CAKyqqaaDqVHtx1h6-kbdNi0ev5LJ4xUFBJLOCLChgf_iVdSjZg@mail.gmail.com>

On 1/7/2021 3:04 PM, Jairo A. del Rio wrote:
> Hmm, it works for Persian because this uses less diacritics than Arabic. 
> The following fails with LMTX:
> 
> \definefontfamily[main][serif][notonaskharabic][features=arabic]
> 
> \setupdirections[bidi=global,method=one]
> 
> \setupbodyfont[main]
> 
> \starttext
> 
> \obeylines
> 
> %https://www.letsstartthinking.org/Islam/quran-short-phrases-and-verses.php 
> <https://www.letsstartthinking.org/Islam/quran-short-phrases-and-verses.php>
> 
> بِسْمِ اللَّـهِ الرَّحْمَـٰنِ الرَّحِيمِ
> 
> \stoptext
> 
> Hi, Hans. Could you please check this out? It works for MKIV, but in 
> LMTX vowels are misplaced. Thank you in advance.

It works here but i have different code in the meantime. We're in a 
transition to an lmtx version of the font handler. In lmtx we need to do 
a bit more checking when we are in in compact font mode so it might be 
that there is temporary loss of some functionality. In principle mkiv 
and lmtx should do the same as there is no real change in logic.)

I'll push an update later today,

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
___________________________________________________________________________________

  reply	other threads:[~2021-01-07 15:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24  7:12 Jairo A. del Rio
     [not found] ` <0f190a2f-ca7f-2c7c-bbc5-a1ccf588a616@xs4all.nl>
     [not found]   ` <CAKyqqaa1Dnnud-DRpzXh49i_sELQEEMH9NdmdBXWc4wdW7ko9A@mail.gmail.com>
2020-11-24 19:17     ` Fwd: " Jairo A. del Rio
2020-11-25 19:21       ` Jairo A. del Rio
2021-01-07  6:33 ` denis.maier
2021-01-07 13:48   ` Jairo A. del Rio
2021-01-07 14:04     ` Jairo A. del Rio
2021-01-07 15:20       ` Hans Hagen [this message]
2021-01-07 16:15         ` Jairo A. del Rio
2021-01-07 22:05           ` RE : " Joseph
2021-01-08 10:46             ` Hans Hagen

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=24267899-2000-b5a7-8f8e-5cc247998bad@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=jairoadelrio6@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).