From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Hebrew vowel placement in ConTeXt.
Date: Fri, 02 May 2014 18:58:36 -0400 [thread overview]
Message-ID: <5364231C.7070806@rik.users.panix.com> (raw)
In-Reply-To: <CAKTWfUMqok2KaH9f20+N6M=+dWsYo4Bj=4_h6EZ1xeULdKH0qg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1636 bytes --]
On 2014-05-02 14:36, Michael Ash wrote:
> May I bump?
>
> The following code used to work, but now it gives an error:
>
> \usemodule[simplefonts]
> \definefontfeature[hebrew][default][mode=node,script=hebr,language=dflt,mark=yes,ccmp=yes]
> \setmainfont[Ezra SIL SR][features=hebrew]
> \setupdirections[bidi=on]
> \starttext
> ?????????? ?????? ????????? ???? ?????????? ?????? ????????
> \stoptext
>
> The following variant (without "script=hebr") compiles but the vowels
> are misplaced (not centered below the letters), which "ccmp=yes" (see
> http://www.microsoft.com/typography/otspec/features_ae.htm#ccmp) is
> supposed to request:
>
> \usemodule[simplefonts]
> \definefontfeature[hebrew][default][mode=node,language=dflt,mark=yes,ccmp=yes]
> \setmainfont[Ezra SIL SR][features=hebrew]
> \setupdirections[bidi=on]
> \starttext
> ?????????? ?????? ????????? ???? ?????????? ?????? ????????
> \stoptext
>
> The problem in definefontfeature seems to be that the feature
> "ccmp=yes" is not taking effect, and the feature "script=hebr"
> generates an error.
>
> Thank you very much for your advice.
>
> Michael
Michael,
Sorry to say, no problem here with your example, and trimming the second
line even further to
\definefontfeature[hebrew][default][script=hebr,ccmp=yes]
still produces results with no errors and proper nikkud alignment (run
on a system running Windows 8.1 x64 and ConTeXt standalone 2014-04-28
standard and jit).
Similarly, no problem with traditional font definition without simplefonts.
What platform are you using, what version of Ezra SIL SR (likely 2.51,
but worth asking)?
--
rik kabel
[-- Attachment #1.2: Type: text/html, Size: 4274 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
___________________________________________________________________________________
prev parent reply other threads:[~2014-05-02 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 16:07 Michael Ash
2013-06-17 16:15 ` Michael Ash
2013-06-17 16:22 ` Idris Samawi Hamid ادريس سماوي حامد
[not found] ` <12604_1371486185_51BF37E9_12604_399_1_op.wytzrxjlpw6hmh@ishamid-pc>
2013-06-17 16:31 ` Michael Ash
2013-06-17 16:42 ` Idris Samawi Hamid ادريس سماوي حامد
2013-06-17 17:16 ` Hans Hagen
2013-06-17 18:18 ` Michael Ash
2014-05-01 5:28 ` Michael Ash
2014-05-02 18:36 ` Michael Ash
2014-05-02 22:58 ` Rik Kabel [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=5364231C.7070806@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).