ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik Kabel via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Rik Kabel <rik@panix.com>
Subject: Re: [NTG-context] Using project-local fonts
Date: Thu, 13 Apr 2023 15:22:14 -0400	[thread overview]
Message-ID: <e17544b5-54df-4329-255b-af6e1e089a14@panix.com> (raw)
In-Reply-To: <88627c80d6a48eebdb72a94fdbc2627b@ens-lyon.fr>


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


On 2023-04-13 11:28, Kalouguine Andre via ntg-context wrote:
>
> Hi,
>
>> i'm not familiar with that approach so can't see what interferes
> The most important change is that I can't update it and I can't put 
> stuff in the system directory nor the user one.
> So I only have access to the project folder, it has to be self-contained.
>> \definefontfamily [ebgaramond] [serif] [ebgaramond] 
>> [features=eb-garamond-normal]
> Apologies, my fault, I forgot a part of my email. I don't want the c-t 
> and s-t ligatures (supposed to be in `hlig`). But I do want the T-h 
> ligature which is supposed to be in `dlig`. So as far as I understand, 
> TeXlive comes with an old version of EB Garamond in which all of them 
> are in `dlig`. Hence my question about self-contained projects with fonts.
> Best regards,
> Andre
>

Andre (and list),

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.

-- 
Rik


[-- Attachment #1.2: Type: text/html, Size: 3592 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
___________________________________________________________________________________

  parent reply	other threads:[~2023-04-13 19:42 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 [this message]
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

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=e17544b5-54df-4329-255b-af6e1e089a14@panix.com \
    --to=ntg-context@ntg.nl \
    --cc=rik@panix.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).