ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Joey McCollum via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Joey McCollum <jmccollum20140511@gmail.com>
Subject: Re: Hebrew punctuation with SBL Hebrew
Date: Wed, 31 Aug 2022 20:24:45 +1000	[thread overview]
Message-ID: <CAGxRUG_4rFm9RNGRVsdKdcmhnG=Fde3dowskL5GQjq4Yf2uX8A@mail.gmail.com> (raw)
In-Reply-To: <e9d147154c114ad3a8490f7b7cf09c99@unibe.ch>


[-- Attachment #1.1: Type: text/plain, Size: 2122 bytes --]

In your "broken" example, the patah below the het is being moved to the
right rather than staying under the middle of the het? But the shift to the
right is the correct behavior for furtive patah and should be expected.

On Wed, Aug 31, 2022 at 8:06 PM Denis Maier via ntg-context <
ntg-context@ntg.nl> wrote:

> Hi,
>
>
>
> I’m running into something weird with Hebrew punctuation. Consider the
> example below. SBL Hebrew gives me incorrect results when there’s a vaw
> with a holam = וֹ  just before a chet with a patach = חַ => the patach
> below the chet ist misplaced.
>
> If I remove the holam from the vaw, everything looks ok. Oddly, in Linux
> Libertine I get the correct results in both cases. Does anyone know what
> the problem is here? User error? A bug in SBL Hebrew (which would be very
> odd since that font should be designed specifically for that kind of
> stuff). A missing seeting?
>
>
>
> Best,
>
> Denis
>
>
>
> \definefontfamily[notok][rm][SBL Hebrew][features=hebrew]
>
> \definefontfamily[ok][rm][Linux Libertine O][features=hebrew]
>
>
>
> \setupdirections[bidi=global,method=unicode]
>
>
>
>
>
> \starttext
>
>
>
> Ok:
>
> {\switchtobodyfont[notok]
>
> חִיוּחוחַ
>
> }
>
>
>
> Broken:
>
> {\switchtobodyfont[notok]
>
> חִיוּחוֹחַ
>
> }
>
>
>
> Linux Libertine works in both cases:
>
>
>
> Ok:
>
> {\switchtobodyfont[ok]
>
> חִיוּחוחַ
>
> }
>
>
>
> Ok:
>
> {\switchtobodyfont[ok]
>
> חִיוּחוֹחַ
>
> }
>
>
>
>
>
> \stoptext
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : https://contextgarden.net
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 5996 bytes --]

[-- Attachment #2: Type: text/plain, Size: 496 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-08-31 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 10:06 Denis Maier via ntg-context
2022-08-31 10:24 ` Joey McCollum via ntg-context [this message]
2022-08-31 12:02   ` Denis Maier via ntg-context

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='CAGxRUG_4rFm9RNGRVsdKdcmhnG=Fde3dowskL5GQjq4Yf2uX8A@mail.gmail.com' \
    --to=ntg-context@ntg.nl \
    --cc=jmccollum20140511@gmail.com \
    /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).