Re: [NTG-context] Hebrew vowel placement in ConTeXt. (Rik Kabel)

2014-05-03 Thread Michael Ash
Thank you very much for the reply.
I switched to ConTeXt standalone and now it is working.

Best,
Michael


This works:

\usemodule[simplefonts]
\definefontfeature[hebrew][default][script=hebr,ccmp=yes]
\setmainfont[Ezra SIL SR][features=hebrew]
\setupdirections[bidi=on]
\starttext
בְרֵאשִ֖ית בָרָ֣א אֱלֹהִ֑ים אֵ֥ת הַשָמַ֖יִם וְאֵ֥ת הָאָֽרֶץ
\stoptext


BTW what is the \definefontfamily syntax that would work with
\setupbodyfont in the new post-simplefonts era?

Best,
Michael

PS Just FYI here is what I had been working with:

What platform are you using, what version of Ezra SIL SR (likely 2.51,
 but worth asking)?


I am using linux (ubuntu 14.04)

fonts-sil-ezra package
Package fonts-sil-ezra:
i   2.51-8 trusty  500
(I presume this means version 2.51.)

I am using the current ppa:reviczky/context-daily version of context:

ConTeXt  ver: 2014.03.25 16:58 MKIV beta  fmt: 2014.5.1  int:
english/english

Here is the error message that I was receiving (when I include
script=hebr):

+ /usr/share/texmf/tex/context/third/simplefonts/t-simplefonts.lua)error:
/usr/share/texmf/tex/context/base/font-otn.lua:805: attempt to call upvalue
'getprop' (a nil value)









  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.


___
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
___

Re: [NTG-context] Hebrew vowel placement in ConTeXt. (Rik Kabel)

2014-05-03 Thread Rik Kabel

On 2014-05-03 17:16, Michael Ash wrote:


Thank you very much for the reply.
I switched to ConTeXt standalone and now it is working.

Best,
Michael


This works:

\usemodule[simplefonts]
\definefontfeature[hebrew][default][script=hebr,ccmp=yes]
\setmainfont[Ezra SIL SR][features=hebrew]
\setupdirections[bidi=on]
\starttext
?? ?? ?  ?? ?? 
\stoptext


BTW what is the \definefontfamily syntax that would work with 
\setupbodyfont in the new post-simplefonts era?


Best,
Michael


As to the by-the-way, see message 56606 
http://www.mail-archive.com/ntg-context%40ntg.nl/msg56606.html in the 
list archive. This is not the post-simplefonts solution, but the 
pre-simplefonts solution. It does allow much better control over all of 
the fonts that make up the typeface (using ConTeXt terminology).


The example shows what to do to set a document that is primarily Hebrew 
(or other RtL script). If you want to mix directions, bidi may be a 
better choice than the setupalign of the example. If you use bidi, I 
suggest \setupdirections[bidi=on,method=two]. I find that without method 
two, there is a problem with punctuation. In particular, the comma in


   some text {\heb **}, some more text

gets set before, not after, the hebrew text.

If you set only some Hebrew/Aramaic/Arabic, and especially if you do not 
need font variants (bold, italic, ...) you might prefer to define a 
single font. I have used:


   \definefontfeature [aramaic]
   [default]
   [ccmp=yes,
script=hebr]
   \definefont[aramaic]%% KeterYG from
   http://culmus.sourceforge.net/taamim/
   [KeterYG-Medium.ttf*aramaic sa 1]
   \setupdirections   [bidi=on=,method=two]
   \starttext
   English {\aramaic  ???} English again.
   \stoptext

I do note as well that there is a problem in the example in the linked 
message. It looks to me like the order of components is beth/shva/dagesh 
(for the first letter (and beth/qamatz/dagesh for the first of the 
second word), which ConTeXt sets incorrectly.  When the order is changed 
to beth/dagesh/qamatz-or-shva, they are set correctly. If you use vim, 
the command ga will show the decomposition of the character components.


Here are the two versions of that letter, first in the order that sets 
correctly:


   ???

and then in the order that does not:

   ???


--
rik

___
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
___