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>
Subject: Re: Arabic with LuaTeX vs. XeTeX
Date: Tue, 10 Jun 2008 10:09:47 +0200	[thread overview]
Message-ID: <484E36CB.4090100@wxs.nl> (raw)
In-Reply-To: <op.uch8n3f7nx1yh1@your-b27fb1c401>

Idris Samawi Hamid wrote:

> 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.

one problem there is that the open type spec is not always clear which 
in turn can mean that apps do things different or maybe even know how to 
deal with certain fonts; another problem is that there is no prescribed 
behaviour ... ok, some dtp app can claim that version n+3 supports this 
or that feature, or adapts automatically to this or that situations but 
if that's then the 'standard' there is no reason why version n+1 should 
not have supported it (or should have been tagged as bugged)

> 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.

we can add all kind of checking and compensation and make them pseudo 
features and then have them enabled based on info that we keep in a font 
database (like .. this font lacks this or that and therefore we need to 
enable such or so; of this feature in font foo is bugged so we disable it)

> 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.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2008-06-10  8:09 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
2008-06-10  8: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=484E36CB.4090100@wxs.nl \
    --to=pragma@wxs.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).