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>,
	"Hans Hagen" <pragma@wxs.nl>
Cc: Michael Saunders <odradek5@gmail.com>
Subject: Re: can Context render complex scripts?
Date: Sun, 13 Jun 2010 14:07:19 -0600	[thread overview]
Message-ID: <op.vd88uh12pw6hmh@ishamid-pc> (raw)
In-Reply-To: <4C153472.7090703@wxs.nl>

Hi,

On Sun, 13 Jun 2010 13:41:38 -0600, Hans Hagen <pragma@wxs.nl> wrote:

> the interesting question then is .. where does one draw the line between  
> engine and clever fonts

contextual analysis in Arabic provides an example: init, medi, and fina  
provide the gsub's, the engine has to know the rules/conditions under  
which to apply each of those three. Eg, VOLT Proofing tool will NOT do  
contextual analysis, only implement the selected lookups. Something  
similar applies to Indic of course, but someone has to provide the  
framework of rules. The MS pages Khaled sent are a good place to start,  
and a user willing to make examples with explanations etc...

That is, given all gsub and gpos routines needed by a given language, what  
minimal additional information does the engine need to know? In Arabic,  
one needs contextual analysis: if a letter occurs at the beginning of a  
string, choose the init gsub routine etc.

The bad thing about Uniscribe is that it adds too much information and  
"spell-checking", restricting typesetting possibilities.

In any case, someone interested has to research/provide the details for  
Indic.

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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2010-06-13 20:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11  7:14 Michael Saunders
2010-06-11  7:49 ` Khaled Hosny
2010-06-13 14:59 ` Hans Hagen
2010-06-13 16:58   ` Michael Saunders
2010-06-13 19:07     ` Hans Hagen
2010-06-13 19:15       ` Khaled Hosny
2010-06-13 19:19         ` Khaled Hosny
2010-06-13 19:28           ` Khaled Hosny
2010-06-13 19:41         ` Hans Hagen
2010-06-13 20:07           ` Idris Samawi Hamid ادريس   سماوي حامد [this message]
2010-06-14  1:21             ` Michael Saunders
2010-06-14  7:57               ` Hans Hagen
2010-06-13 19:29       ` Michael Saunders
2010-06-13 19:50         ` Khaled Hosny
2010-06-13 20:08           ` 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.vd88uh12pw6hmh@ishamid-pc \
    --to=ishamid@colostate.edu \
    --cc=ntg-context@ntg.nl \
    --cc=odradek5@gmail.com \
    --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).