ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Michael Saunders <odradek5@gmail.com>
To: ntg-context@ntg.nl
Cc: pragma@wxs.nl, ishamid@colostate.edu
Subject: Re: can Context render complex scripts?
Date: Sun, 13 Jun 2010 11:58:27 -0500	[thread overview]
Message-ID: <AANLkTimT7lBCSiQPB9GPE-oDY3_q5snSt3UoaeKgXiji@mail.gmail.com> (raw)
In-Reply-To: <4C14F250.70206@wxs.nl>

> next time make a simple example .. you caniidentity features with
>
> mtxrun --script font --info --list --file BNBDOT0N.ttf
>
> anyhow, only one features is applied. It lookslike some gpos feature is not
> used.
>
> \usemodule[fnt-20]
>
> \definefontfeature
>  [indic]
>  [mode=node,analyze=yes,
>   script=beng,language=dflt,
>   % gsub
>   abvs=yes,akhn=yes,blwf=yes,blws=yes,
>   half=yes,nukt=yes,pstf=yes,psts=yes,rphf=yes,
>   % gpos
>   blwm=yes,abvm=yes]
>
> \definefontsynonym[dwbangla][file:BNBDOT0N.ttf]
>
> \starttext
>
>    {\definedfont[dwbangla*indic] সত্যজিৎ রায় \par}
>
>    \showotfcomposition
>        {dwbangla*indic}
>        {0}
>        {সত্যজিৎ রায়}
>
> \stoptext


I don't understand---are you saying this is supposed to work?  Is the
trick supposed to be using fnt-20 or in being careful not to turn on
unused features?  (To be on the safe side, since I was switching
between them in testing, I was turning on all the features Microsoft
calls Indic.)  I tried your example and, yes, one shaping looks
correct, but there was no reordering and now some of the characters
print out on top of each other (which is incorrect).  I tried the same
routine, using  fnt-20 and commenting out unused features, for some
other fonts:
Akaash:
http://www.nongnu.org/freebangfont/downloads.html
Bangla, from the University of Chicago:
http://salrc.uchicago.edu/resources/fonts/available/bengali/
and Arial Unicode MS  (standard on Windows),
and I got no improvement in their rendering in Context.  They work
fine in Notepad, Firefox, and TexnicCenter though, for example.

What am I missing?
___________________________________________________________________________________
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 16:58 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 [this message]
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

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=AANLkTimT7lBCSiQPB9GPE-oDY3_q5snSt3UoaeKgXiji@mail.gmail.com \
    --to=odradek5@gmail.com \
    --cc=ishamid@colostate.edu \
    --cc=ntg-context@ntg.nl \
    --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).