From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Joey McCollum <jmccollum20140511@gmail.com>
Subject: Re: Fwd: Unicode normalization and Hebrew in ConTeXt
Date: Tue, 28 Apr 2020 20:03:09 +0200 [thread overview]
Message-ID: <07e2f068-926a-89d7-3d94-ab785ac5a498@xs4all.nl> (raw)
In-Reply-To: <CAGxRUG-TK=NoEQ4hBtRD=cX66tO1XJjkcp=v6ewudYTpT-YxRw@mail.gmail.com>
On 4/28/2020 6:16 PM, Joey McCollum wrote:
> Thank you for the prompt and thorough response!
>
> If the reorderings have to be done for each pair of characters in
> different combining classes that are not in the expected typographical
> order, then there will be a lot (probably hundreds) of substitution
> rules. I am not very familiar with coding in Lua, but if there is a way
> to add substitution features for specific classes of points, then that
> would require a lot fewer cases.
don't worry about that now, the lua part is normally the easy part (a
where-it-makes-most-sense-hooking-into could take more thinking)
(i have been thinking of some additional feature mechanisms but have to
find back some code i played with long ago)
> Unicode's canonical ordering of Hebrew marks is based on their combining
> classes, with characters in higher combining classes being sorted after
> those with lower combining classes in canonical order. The
> typographically recommended ordering of certain characters is found in
> Table 1 (p. 12) of
> https://www.sbl-site.org/Fonts/SBLHebrewUserManual1.5x.pdf. The
So how official is that? Or is this something specific for this font?
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2020-04-28 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 11:59 Joey McCollum
2020-04-28 13:17 ` Hans Hagen
[not found] ` <CAGxRUG_cyT1XfYTvTh23+LaVg4an8exL-LZYfbZUOf+s2XvRRQ@mail.gmail.com>
2020-04-28 16:16 ` Fwd: " Joey McCollum
2020-04-28 18:03 ` Hans Hagen [this message]
2020-04-28 18:21 ` Hans Hagen
2020-04-28 19:06 ` Joey McCollum
2020-04-30 19:40 ` Arthur Reutenauer
2020-04-30 9:26 ` Hans Hagen
2020-04-30 14:28 ` Joey McCollum
2020-04-30 15:14 ` Hans Hagen
2020-04-30 20:17 ` Joey McCollum
2021-08-17 0:07 ` Joey McCollum via ntg-context
2021-08-17 9:19 ` Hans Hagen via ntg-context
2021-08-17 12:56 ` Joey McCollum via ntg-context
2021-08-17 19:46 ` Joey McCollum via ntg-context
2021-08-18 13:19 ` Hans Hagen 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=07e2f068-926a-89d7-3d94-ab785ac5a498@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=jmccollum20140511@gmail.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).