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>
Cc: Michael Saunders <odradek5@gmail.com>
Subject: Re: can Context render complex scripts?
Date: Mon, 14 Jun 2010 09:57:36 +0200	[thread overview]
Message-ID: <4C15E0F0.5070608@wxs.nl> (raw)
In-Reply-To: <AANLkTikrCPkaYBEmGaAlsKo78cY4RUL_xaE-p9xrHbS9@mail.gmail.com>

On 14-6-2010 3:21, Michael Saunders wrote:
>> 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 you want to use external engines ... use xetex instead of luatex

the whole idea behind luatex is that we have a configureable and 
programmable engine ... doing some script is not so much an issue (and 
we can do it more flexible once we have the machinery in place) but 
information is needed ... also, as we want tex cum suis to be flexible 
on the one hand and stable on the other, depending on hidden or fuzzy 
features in en uniscribe engine might not be the best idea

in the oriental tex project we've spend quite some time on high quality 
arabic and i'm sure that we could not have come this far if we had wrote 
the code from scratch (all this font technology is not as open as the 
name suggest) ... also, there's more in mkiv than shown so far (esp in 
that area) for those experiments


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
___________________________________________________________________________________


  reply	other threads:[~2010-06-14  7:57 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 [this message]
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=4C15E0F0.5070608@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=odradek5@gmail.com \
    /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).