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: "Eigner, G.C." <g.c.eigner@vu.nl>
Subject: Re: Installing an arabic font
Date: Thu, 09 May 2013 12:55:01 +0200	[thread overview]
Message-ID: <518B8085.90901@wxs.nl> (raw)
In-Reply-To: <518B5408.6080706@mmnetz.de>

On 5/9/2013 9:45 AM, "H. Özoguz" wrote:
>> The font is fine with other
>> OpenType engines as well, e.g. HarfBuzz, so it is probably a ConTeXt
>> issue.
>
> Yes, the font is fine with OpenOffice, too.
> It would be really great, if this could be fixed in context, so one
> could typeset quran (and other traditional arabic) professionally. Would
> be very valuable!

I uploaded a beta that might fix it, but it needs more testing. The 
issue might have been introduced when support was added for more complex 
ligature building, compare for instance this:

\starttext

\def\sample{نَسْتَعِينُ وَلَا الضَّالِّينَ}
\def\sample{نَسْتَعِينُ}
\def\sample{\Uchar"0643\Uchar"0644\Uchar"0651\Uchar"0627\Uchar"064E}

\setvariables
   [otftracker]
   [font=file:uthmantn1ver10.ttf,
    size=24pt,
    features=arabic,
    direction=-1,
    title=Feature Check,
    sample=\sample]

\page

\setvariables
   [otftracker]
   [font=file:arabtype,
    size=24pt,
    features=arabic,
    direction=-1,
    title=Feature Check,
    sample=\sample]

\stoptext

(So Kai needs to run some of his tests.)

Hans

ps. some of the somewhat complex implementation will be redone when we 
have a pending extension to glyph nodes in the engine done.

-----------------------------------------------------------------
                                           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:[~2013-05-09 10:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09  7:45 "H. Özoguz"
2013-05-09 10:55 ` Hans Hagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-05-09 17:27 "H. Özoguz"
2013-05-10  8:35 ` Hans Hagen
2013-05-08 20:58 "H. Özoguz"
2013-05-08 21:03 ` Hans Hagen
2013-05-09  7:08   ` Khaled Hosny
2013-05-08 19:23 "H. Özoguz"
2013-05-08 20:16 ` Hans Hagen
2013-05-08 15:39 "H. Özoguz"
     [not found] <518A03E1.6070705@mmnetz.de>
2013-05-08 15:38 ` "H. Özoguz"
2013-05-08 16:28   ` Khaled Hosny

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=518B8085.90901@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=g.c.eigner@vu.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).