From: Hans Hagen <pragma@wxs.nl>
To: Khaled Hosny <khaledhosny@eglug.org>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: can Context render complex scripts?
Date: Sun, 13 Jun 2010 22:08:06 +0200 [thread overview]
Message-ID: <4C153AA6.40609@wxs.nl> (raw)
In-Reply-To: <20100613195056.GA4265@khaled-laptop>
On 13-6-2010 9:50, Khaled Hosny wrote:
> So, what we have here is that ConTeXt has no special knowledge about
> Indic scripts, and thus it will not apply the feature properly according
> the linguistic rules. So, instead of waiting for a "more modern font to
> come along" (which unlikely to happen any time soon, giving how much the
> industry have invested into OpenType, and the apparent failure of AAT),
> just try to reach more people in the Indic community and come out with a
> clear specification and tests that Hans can implement.
from the ms pages it looks like we should split the chars (sequences)
into components and after that the oft features can be applied; as the
spec is somewhat fuzzy i'll just wait till precise specs are given
Hans
-----------------------------------------------------------------
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-06-13 20:08 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 ادريس سماوي حامد
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 [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=4C153AA6.40609@wxs.nl \
--to=pragma@wxs.nl \
--cc=khaledhosny@eglug.org \
--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).