ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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 17:37:28 +0200	[thread overview]
Message-ID: <f8e0854e-2fcb-733e-5027-a46f90ceb454@xs4all.nl> (raw)
In-Reply-To: <88627c80d6a48eebdb72a94fdbc2627b@ens-lyon.fr>

On 4/13/2023 5:28 PM, 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.
You can put the font in the local directory but i have no clue how that 
works with your setup because in the end the font cache is used and does 
a user have a local one? YOu can maybe rename the font,. put it in the 
work directory and make a typescript that refers to that one.

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
___________________________________________________________________________________

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

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=f8e0854e-2fcb-733e-5027-a46f90ceb454@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).