From: Rik Kabel <context@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: newotf definefontfeatures problem with script=hebr
Date: Sun, 12 Jul 2015 13:02:53 -0400 [thread overview]
Message-ID: <55A29DBD.4040002@rik.users.panix.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1986 bytes --]
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
The same problem occurs in the same way with the following fonts, most
of which are shipped with Windows:
Arial Regular
Arial Bold
Arial Narrow
David Regular
David Bold
Ezra SIL Regular
Ezra SIL SR Regular
Keter YG Medium
Levenim MT Regular
Levenim MT Bold
Taamey David CLM
Tahoma Regular
Tahoma Bold
Times New Roman Regular
Times New Roman Bold
[-- Attachment #1.2: Type: text/html, Size: 2953 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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 reply other threads:[~2015-07-12 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 17:02 Rik Kabel [this message]
2015-07-12 21:35 ` 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=55A29DBD.4040002@rik.users.panix.com \
--to=context@rik.users.panix.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).