ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Michael Saunders <odradek5@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: can Context render complex scripts?
Date: Sun, 13 Jun 2010 20:21:09 -0500	[thread overview]
Message-ID: <AANLkTikrCPkaYBEmGaAlsKo78cY4RUL_xaE-p9xrHbS9@mail.gmail.com> (raw)
In-Reply-To: <op.vd88uh12pw6hmh@ishamid-pc>

> OpenType (just ignore file extension for the moment) is a rather dump
> standard in the sense that it requires the engine to have some knowledge
> about the writing system at hand.
...
> 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.

It seems to me that, since Hans can't be expected to write special
code for dozens of Indic scripts, let alone for every script in the
world, the pragmatic solution would be a method for Context to harness
external engines (ICU, Pango, Graphite, Uniscribe, or whatever).  If
that's not possible, or if he doesn't want to do it, or until he is
able to work with scholars on each special case, programs like Notepad
will be able to do something that Context can't.   As a casual user,
it's not an urgent need for me.  I had read that Aleph functionality
had been integrated into LuaTeX (though I never found anything very
detailed about that) and thought that everything was okay.  I assume
that Luatex/Context or some future TeX  will have this functionality
someday, however it's implemented.  I'll just keep watching.
___________________________________________________________________________________
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-14  1:21 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 [this message]
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=AANLkTikrCPkaYBEmGaAlsKo78cY4RUL_xaE-p9xrHbS9@mail.gmail.com \
    --to=odradek5@gmail.com \
    --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).