ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Idris Samawi Hamid" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Arabic with LuaTeX vs. XeTeX
Date: Mon, 09 Jun 2008 17:25:05 -0600	[thread overview]
Message-ID: <op.uch8n3f7nx1yh1@your-b27fb1c401> (raw)
In-Reply-To: <E3E43AFF-D4F6-4649-BAAC-62FE615E891D@gmail.com>

Hi Otared and all,

On Mon, 09 Jun 2008 03:13:06 -0600, Otared Kavian <otared@gmail.com> wrote:

> I just read the thread started by Burak Emir about "Typesetting Arabic
> today", and tried to typeset the sample sent by Idris Samawi Hamid.
> One of the Arabic or Persian fonts that I have and LuaTeX can find is
> Nadeem (working on Mac OS X 10.5.3), but what I get after typesetting
> is the following attached PDF: all the characters are typeset with
> their isolated form. However typestting the same text with XeConTeXt
> or XeTeX gives a nice result.

As Khaled and Wolfgang already intimated, the problem is that Nadeem is  
not an OpenType font, but rather AAT. XeTeX is mainly Mac-based so it's  
natural that it supports AAT.

It should not be too hard to overload GSUB and GPOS features for this  
particular font using the fea file overload feature of luatex (not sure if  
that has been fixed.)

I looked at the AAT code, and saved an fea file using FontForge: but the  
contextual analysis is not there, so I suspect that AAT fonts depend on  
something like uniscribe for certain basic features. We (=Hans) need to  
know what that is.

But at this stage of development, only pure OpenType fonts will be  
supported out of the box. For example: Traditional Arabic, which comes  
with XP, has OpenType tables but depends on Uniscribe instead of OpenType  
for, eg, making marks exceptions to the contextual analysis. Since the  
mark exception was not added to the GSUB table, voweled text appears  
unjoined in Trad. Arabic processed by luaTeX.

I suppose we (=Hans) could add some "spell-checking" to the otf analyzer,  
but that's dangerous and needs some careful thought. Maybe we can come up  
with various "spell-checking" options that could be turned on and off, so  
that old-technology (Nadeem is 1998), platform-dependent (like Nadeem and  
Trad. Ar.) fonts can be used.

In any case, we want to stay as platform-independent as possible. So for  
AAT, we may need to wait at least till someone (maybe one of you?) can  
come up with a spec so that we can implement a cross-platform solution for  
AAT.

Best wishes
Idris

-- 
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2008-06-09 23:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09  9:13 Otared Kavian
2008-06-09  9:23 ` Wolfgang Schuster
2008-06-09 11:38   ` Otared Kavian
2008-06-09 15:09     ` Burak Emir
2008-06-09 15:21       ` Otared Kavian
2008-06-09 16:07         ` Hans Hagen
2008-06-09 16:43           ` Otared Kavian
2008-06-09 16:53             ` Mojca Miklavec
2008-06-09 20:45               ` Otared Kavian
2008-06-09 21:09                 ` Hans Hagen
2008-06-09 21:40               ` Oliver Buerschaper
2008-06-09 17:00             ` Hans Hagen
2008-06-09 17:03             ` Burak Emir
2008-06-09 11:52 ` Khaled Hosny
2008-06-09 12:00   ` Wolfgang Schuster
2008-06-09 14:52 ` Idris Samawi Hamid
2008-06-09 23:25 ` Idris Samawi Hamid [this message]
2008-06-10  8:09   ` 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=op.uch8n3f7nx1yh1@your-b27fb1c401 \
    --to=ishamid@colostate.edu \
    --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).