From: Lutz Haseloff <lutz.haseloff@toppkieker.info>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with vocalised hebrew
Date: Fri, 15 Dec 2017 20:11:00 +0100 [thread overview]
Message-ID: <89DEDF0C-13B0-4DFD-AC71-2EC062508E84@toppkieker.info> (raw)
In-Reply-To: <c29d71b4-4e5f-946d-dd40-316df1146983@rik.users.panix.com>
[-- Attachment #1.1: Type: text/plain, Size: 2191 bytes --]
Thank you very much Rik,
your settings for EzraSIL are working nicely for my favorite font Narkisim.
Thanks again
Lutz
Am 15. Dezember 2017 19:09:09 MEZ schrieb Rik Kabel <context@rik.users.panix.com>:
>On 2017-12-15 06:45, Lutz Haseloff wrote:
>> Hi all,
>> i would like to typeset hebrew with context.
>> My not fully working example:
>>
>> \starttext
>> \definedfont[name:narkisim at 20pt]
>> \setupalign[r2l]
>> טְרוֹפוֹתִי
>> \stoptext
>>
>> In the resulting pdf the vocalisations are on the left side of the
>> glyph, instead of being centered.
>> I append the result of context and the result of Libreoffice.
>>
>> Is there a way to typeset vocalised hebrew with context or am I doing
>
>> something wrong?
>>
>> Greetings Lutz
>> --
>> GPG Key ID 3C4F83BC
>>
>>
>>
>___________________________________________________________________________________
>> 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://context.aanhet.net
>> archive : https://bitbucket.org/phg/context-mirror/commits/
>> wiki : http://contextgarden.net
>>
>___________________________________________________________________________________
>
>Depending on the font, correct niqqud placement requires some
>combination (sometimes all) of the following font features: lang, ccmp,
>
>and script. For Ezra SIL, I would use
>
> \definefontfeature [hebrew] [oldstyle] [
> lang=heb,
> ccmp=yes,
> script=hebr,
> ]
> \starttext
> \definedfont[name:EzraSIL*hebrew at 72pt]
> \setupalign[r2l]
> טְרוֹפוֹתִי
> \stoptext
>
>while for David_CLM the script feature suffices:
>
> \definefontfeature [hebrew] [oldstyle] [
> % lang=heb,
> % ccmp=yes,
> script=hebr,
> ]
> \starttext
> \definedfont[name:David_CLM-medium*hebrew at 72pt]
> \setupalign[r2l]
> טְרוֹפוֹתִי
> \stoptext
>
>You will have to find what works for narkisim.
>
>--
>Rik
--
GPG Key ID 3C4F83BC
[-- Attachment #1.2: Type: text/html, Size: 3881 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-12-15 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 11:45 Lutz Haseloff
2017-12-15 18:09 ` Rik Kabel
2017-12-15 19:11 ` Lutz Haseloff [this message]
2017-12-15 21:54 ` Henning Hraban Ramm
2017-12-16 6:31 ` Lutz Haseloff
2017-12-16 8:23 ` 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=89DEDF0C-13B0-4DFD-AC71-2EC062508E84@toppkieker.info \
--to=lutz.haseloff@toppkieker.info \
--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).