From: Rajeesh K Nambiar <rajeeshknambiar@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: devanagari rendering (2 errors)
Date: Tue, 10 Sep 2013 18:42:30 +0200 [thread overview]
Message-ID: <CA+BbHh7q3wmkaiYQo5zKNk50Dg_xJgH20MzTyuv56yU+0WBG4Q@mail.gmail.com> (raw)
In-Reply-To: <522F0AB9.5090301@wxs.nl>
Hi Hans,
On Tue, Sep 10, 2013 at 2:04 PM, Hans Hagen <pragma@wxs.nl> wrote:
>
> it took me quite a while to notice that it's a side effect of two features
> that are turned on
>
> you can play with
>
> \definefontfeature
> [devanagari-one]
> [devanagari-one]
> [rphf=no]
>
> and
>
> \definefontfeature
> [devanagari-one]
> [devanagari-one]
> [half=no]
>
> maybe Kai can have a look at it: as these are dealt with in a different we
> probably don't need to enable them in the feature processor (even block
> them)
>
As far as I understand, 'rphf' and 'half' forms are essential for
Devanagari, so skipping them completely might not be a good idea...
> btw, you can play with
>
> \showotfcomposition{file:chandas.ttf*devanagari-one}{l2r}{\char"0915
> \char"094D \char"0930}
>
--
Cheers,
Rajeesh
___________________________________________________________________________________
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:[~2013-09-10 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 20:05 Peter Graif
2013-09-09 22:22 ` Hans Hagen
2013-09-10 4:43 ` Peter Graif
2013-09-10 12:04 ` Hans Hagen
2013-09-10 15:44 ` Peter Graif
2013-09-10 16:42 ` Rajeesh K Nambiar [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=CA+BbHh7q3wmkaiYQo5zKNk50Dg_xJgH20MzTyuv56yU+0WBG4Q@mail.gmail.com \
--to=rajeeshknambiar@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).