From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: newotf definefontfeatures problem with script=hebr
Date: Sun, 12 Jul 2015 23:35:57 +0200 [thread overview]
Message-ID: <55A2DDBD.7050900@wxs.nl> (raw)
In-Reply-To: <55A29DBD.4040002@rik.users.panix.com>
On 7/12/2015 7:02 PM, Rik Kabel wrote:
> The following code fails; however, it succeeds without newotf, and it
> succeeds with newotf if the defined font feature (*hebrew) is removed
> from the \definefont command. The characters that demonstrate the
> problem are HEBREW LETTER LAMED combined with HEBREW POINT HOLAM,
> followed by HEBREW LETTER ALEF (U05DC with combining U05B9 followed by
> U05D0). I have not come across other combinations that cause the
> problem, but I have not done an exhaustive search.
>
> \usemodule [newotf]
> \setupdirections [bidi=global]
> \definefontfeature [hebrew] [default] [lang=heb,ccmp=yes,script=hebr]
>
> \definefont [Hebrew] [sileot*hebrew]
> \starttext
> \startTEXpage
> This is okay:{\hfill\Hebrew לא}
>
> This is okay:{\hfill{\Hebrew לֹ}}
>
> This fails:{\hfill{\Hebrew לֹא}}
> \stopTEXpage
> \stoptext
>
> It reports:
>
> error:
> C:/ConTeXt/tex/texmf-context/tex/context/base/font-ots.lua:1586:
> attempt to index a number value
>
> tex error > tex error on line 13 in file
> C://Users/rik/Desktop/newotf-features.tex: ?
>
> <inserted text> \par
>
> <to be read again>
> \vss
> \pack_framed_do_bottom ...amedparameter \c!bottom
> \raggedbottomcommand
> <to be read again> \localendstrut \pack_framed_do_bottom
> \egroup
> \stopfittingpage ->\removeunwantedspaces \egroup
> \egroup \doif
> {\fittingpage...
> l.13 \stopTEXpage
fixed (i only tested siltot)
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
___________________________________________________________________________________
prev parent reply other threads:[~2015-07-12 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 17:02 Rik Kabel
2015-07-12 21:35 ` Hans Hagen [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=55A2DDBD.7050900@wxs.nl \
--to=pragma@wxs.nl \
--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).