From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Hebrew vowel placement in ConTeXt. (Rik Kabel)
Date: Sat, 03 May 2014 19:52:43 -0400 [thread overview]
Message-ID: <5365814B.2070606@rik.users.panix.com> (raw)
In-Reply-To: <CAKTWfUPqPiucAtArzW6bzFUsMg=v0M623LZtSUw5=QJj0aF1tQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2493 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 6102 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-03 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 21:16 Michael Ash
2014-05-03 23:52 ` 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=5365814B.2070606@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).