ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: Arabic typesetting, one more
Date: Sun, 12 May 2013 10:23:35 +0200	[thread overview]
Message-ID: <20130512082335.GB27636@khaled-laptop> (raw)
In-Reply-To: <op.wwxuzhuepw6hmh@ishamid-pc>

On Sat, May 11, 2013 at 03:22:27PM -0600, Idris Samawi Hamid ادريس   سماوي حامد wrote:
> Salaam, Huseyin,
> 
> I missed this and other threads, it's been busy here...
> 
> On Tue, 07 May 2013 23:35:25 -0600, H. Özoguz <h.oezoguz@mmnetz.de> wrote:
> 
> >But with traditionalarabic it is worse than with arabtype. What
> >could be a way to fix this?
> 
> Traditional Arabic is a uniscribe-compliant font, but not a fully
> opentype font. Uniscribe also supports older, pre-unicode protocols.
> In other words, TraditionalArabic is platform-dependent. So unless
> M$ has updated it in a recent OS, it will not work in ConTeXt MkIV.

It did (all its fonts actually), it now uses GPOS for mark placement.

> Since XeTeX uses the local libraries, then mkii/xetex on windows
> might work.

XeTeX does not use any system libraries for its OpenType layout, in the
past is was using ICU LayoutEngine and now it is using HarfBuzz, in all
platforms (i.e. a third party library, but not a system one). However,
HarfBuzz has heuristics to place marks based on glyph bounding boxes in
the case of GPOS absence (a bit similar to TeX's \accent but knows which
marks goes above or below or off the center).

Regards,
Khaled
___________________________________________________________________________________
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-12  8:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08  5:35 "H. Özoguz"
2013-05-08  8:18 ` Hans Hagen
2013-05-11 21:22 ` Idris Samawi Hamid ادريس   سماوي حامد
2013-05-12  8:23   ` Khaled Hosny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-05-07 18:10 "H. Özoguz"
2013-05-07 19:31 ` Hans Hagen
2013-05-07 11:32 "H. Özoguz"
2013-05-07 17:11 ` Hans Hagen
2013-05-07 11:31 "H. Özoguz"
2013-05-06  5:56 "H. Özoguz"
2013-05-03 17:29 "H. Özoguz"

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=20130512082335.GB27636@khaled-laptop \
    --to=khaledhosny@eglug.org \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).