From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Kalouguine Andre via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: [NTG-context] Using project-local fonts
Date: Thu, 13 Apr 2023 22:40:51 +0200 [thread overview]
Message-ID: <9e4c2b49-1e78-2862-223d-b6c454401d31@xs4all.nl> (raw)
In-Reply-To: <bbfdca37129c07e2e201af88d02c5894@ens-lyon.fr>
On 4/13/2023 10:11 PM, Kalouguine Andre via ntg-context wrote:
> On 13.04.2023 21:22, Rik Kabel via ntg-context wrote:
>
>> EB Garamond is hopelessly broken with respect to hlig and dlig, and
>> has been for quite a while.
>>
>> I reported the problem
>> (https://github.com/octaviopardo/EBGaramond12/issues/20) over five
>> years ago, and the maintainer (if there is one) has done nothing. See
>> also #4 in that issues list
>> (https://github.com/octaviopardo/EBGaramond12/issues/4). There are a
>> couple of forks, but there is no established reference implementation
>> that I can see. The Google Fonts implementation is similarly
>> challenged, perhaps worse.
>>
> Oh, I hadn't realized. I had read somewhere that the TeXlive version was
> simply older than the `Specimen.pdf` document and had some bugs. I
> hadn't realized that it wasn't fixed yet.
> This is unfortunate!
>
> Thanks for the information, you saved me from wasting too much time on that.
the lmtx installation comes with some fonts that we keep from the garden
related git repository so we have control over updates; we can do
somethign similar with popular fonts that we like to be frozen in which
case we can tweak them runtime (when we update we can then reconsider
tweaks)
sometimes it's easier to just accept that there are bugs and fix them
runtime
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 / 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
___________________________________________________________________________________
prev parent reply other threads:[~2023-04-13 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 12:06 Kalouguine Andre via ntg-context
2023-04-13 14:32 ` Hans Hagen via ntg-context
2023-04-13 15:28 ` Kalouguine Andre via ntg-context
2023-04-13 15:37 ` Hans Hagen via ntg-context
2023-04-13 19:22 ` Rik Kabel via ntg-context
2023-04-13 20:11 ` Kalouguine Andre via ntg-context
2023-04-13 20:33 ` Hans Hagen via ntg-context
2023-04-13 20:40 ` Hans Hagen via ntg-context [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=9e4c2b49-1e78-2862-223d-b6c454401d31@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).