From: Peter Graif <pgraif@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: devanagari rendering (2 errors)
Date: Tue, 10 Sep 2013 00:43:37 -0400 [thread overview]
Message-ID: <7FE3820F-56A9-4628-9447-E2C1DE305C72@gmail.com> (raw)
In-Reply-To: <522E4A21.2090905@wxs.nl>
>
> Can you make a as-small-as-possible test file?
>
> Preferable with proper utf-8 sequences (+ comment mentioning numbers/classes), good and wrong.
>
> I can probably figure it out but I cannot read or input easily this kind of scripts.
>
> Hans
>
Sure thing. I don't understand how opentype features are represented nor how the ligature logic is dividd up between the font and the engine, so I'm not quite sure what information is helpful or relevant. But, here's a minimal document that contains all the problem sequences I've identified.
As a rough guide, here's another image with the current ConTeXt rendering in black and the desired rendering in red:
http://i.imgur.com/MyvMneg.png
Is that the information you need? Or is there something else I can do?
-Peter
-----------------
\definefont [DevaOne] [file:chandas.ttf*devanagari-one at 16pt]
\starttext
\DevaOne
% The following combinations render incorrectly.
% They are all of the following form:
% {consonant(s)} + U+094D + U+0930
\char"0915 \char"094D \char"0930 ~
\char"0916 \char"094D \char"0930 ~
\char"0917 \char"094D \char"0930 ~
\char"0918 \char"094D \char"0930 ~
\char"0919 \char"094D \char"0930 ~
\char"091A \char"094D \char"0930 ~
\char"091B \char"094D \char"0930 ~
\char"091C \char"094D \char"0930 ~
\char"091D \char"094D \char"0930 ~
\char"091E \char"094D \char"0930 ~\crlf
\char"091F \char"094D \char"0930 ~
\char"0920 \char"094D \char"0930 ~
\char"0921 \char"094D \char"0930 ~
\char"0922 \char"094D \char"0930 ~
\char"0923 \char"094D \char"0930 ~
\char"0924 \char"094D \char"0930 ~
\char"0925 \char"094D \char"0930 ~
\char"0926 \char"094D \char"0930 ~
\char"0927 \char"094D \char"0930 ~
\char"0928 \char"094D \char"0930 ~\crlf
\char"0929 \char"094D \char"0930 ~
\char"092A \char"094D \char"0930 ~
\char"092B \char"094D \char"0930 ~
\char"092C \char"094D \char"0930 ~
\char"092D \char"094D \char"0930 ~
\char"092E \char"094D \char"0930 ~
\char"092F \char"094D \char"0930 ~
\char"0930 \char"094D \char"0930 ~
\char"0931 \char"094D \char"0930 ~
\char"0932 \char"094D \char"0930 ~\crlf
\char"0933 \char"094D \char"0930 ~
\char"0934 \char"094D \char"0930 ~
\char"0935 \char"094D \char"0930 ~
\char"0936 \char"094D \char"0930 ~
\char"0937 \char"094D \char"0930 ~
\char"0938 \char"094D \char"0930 ~
\char"0939 \char"094D \char"0930 ~
\char"0958 \char"094D \char"0930 ~
\char"0959 \char"094D \char"0930 ~
\char"095A \char"094D \char"0930 ~
\char"095B \char"094D \char"0930 ~
\char"095C \char"094D \char"0930 ~
\char"095D \char"094D \char"0930 ~
\char"095E \char"094D \char"0930 ~
\char"095F \char"094D \char"0930 ~
\crlf \crlf \crlf
% The following cominations also render incorrectly.
% The problem occurs at the end of words with sequences:
% {consonant(s)} + U+094D + [end of word]
\char"0915 \char"094D ~
\char"0916 \char"094D ~
\char"0917 \char"094D ~
\char"0918 \char"094D ~
\char"0919 \char"094D ~
\char"091A \char"094D ~
\char"091B \char"094D ~
\char"091C \char"094D ~
\char"091D \char"094D ~
\char"091E \char"094D ~\crlf
\char"091F \char"094D ~
\char"0920 \char"094D ~
\char"0921 \char"094D ~
\char"0922 \char"094D ~
\char"0923 \char"094D ~
\char"0924 \char"094D ~
\char"0925 \char"094D ~
\char"0926 \char"094D ~
\char"0927 \char"094D ~
\char"0928 \char"094D ~\crlf
\char"0929 \char"094D ~
\char"0929 \char"094D ~
\char"092A \char"094D ~
\char"092C \char"094D ~
\char"092D \char"094D ~
\char"092E \char"094D ~
\char"092F \char"094D ~
\char"0930 \char"094D ~
\char"0931 \char"094D ~
\char"0932 \char"094D ~\crlf
\char"0933 \char"094D ~
\char"0934 \char"094D ~
\char"0935 \char"094D ~
\char"0936 \char"094D ~
\char"0937 \char"094D ~
\char"0938 \char"094D ~
\char"0939 \char"094D ~
\char"0958 \char"094D ~
\char"0959 \char"094D ~
\char"095A \char"094D ~
\char"095B \char"094D ~
\char"095C \char"094D ~
\char"095D \char"094D ~
\char"095E \char"094D ~
\char"095F \char"094D ~
\stoptext
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-09-10 4:43 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 [this message]
2013-09-10 12:04 ` Hans Hagen
2013-09-10 15:44 ` Peter Graif
2013-09-10 16:42 ` Rajeesh K Nambiar
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=7FE3820F-56A9-4628-9447-E2C1DE305C72@gmail.com \
--to=pgraif@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).