From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Youssef Cherem <ycherem@gmail.com>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Fallback fails for Linux Libertine O to Junicode over private area, debugging?
Date: Fri, 7 Jan 2022 19:33:55 +0100 [thread overview]
Message-ID: <94850e57-3535-a879-b2aa-33e745b0af57@xs4all.nl> (raw)
In-Reply-To: <m0pmp3a31x.fsf@virginia.edu>
On 1/7/2022 5:59 PM, J. P. Ascher via ntg-context wrote:
> Thanks for asking!
>
> It's just my example. I maintain JunicodeRX (...with Restoration
> Typographical Extensions) which includes yet more non-standard code
> points and which I continue to add to. In my actual work, I also add in
> Symbola for additional fallbacks.
>
> Some fonts have better language coverage (Libertine) and others have
> some custom glyphs I want (JunicodeRX and Symbola). If I had a bit more
> time, I suspect maintaining a stand-alone
> Libertine+JunicodeRX+Symbola.otf would be the best approach, but that's
> a bit beyond me these days.
the complication in mixing fonts is that one cannot really mix the
features arbitrary
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:[~2022-01-07 18:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 15:18 J. P. Ascher via ntg-context
2022-01-07 16:52 ` Youssef Cherem via ntg-context
2022-01-07 16:59 ` J. P. Ascher via ntg-context
2022-01-07 18:33 ` Hans Hagen via ntg-context [this message]
2022-01-07 17:10 ` Hans Hagen via ntg-context
2022-01-07 18:55 ` J. P. Ascher via ntg-context
2022-01-07 19:19 ` Hans Hagen via ntg-context
2022-01-07 21:39 ` J. P. Ascher via ntg-context
2022-01-07 22:01 ` Why mtxrun fails ? Jean-Pierre Delange via ntg-context
2022-01-07 22:40 ` Otared Kavian via ntg-context
2022-01-07 23:00 ` Youssef Cherem via ntg-context
2022-01-08 0:42 ` Jean-Pierre Delange via ntg-context
2022-01-08 0:48 ` Jean-Pierre Delange via ntg-context
2022-01-08 0:45 ` Jean-Pierre Delange via ntg-context
2022-01-08 8:05 ` juh via ntg-context
2022-01-08 10:42 ` Fallback fails for Linux Libertine O to Junicode over private area, debugging? Hans Hagen via ntg-context
2022-01-07 18:23 ` Hans Hagen via ntg-context
2022-01-07 19:11 ` J. P. Ascher 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=94850e57-3535-a879-b2aa-33e745b0af57@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.nl \
--cc=ycherem@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).