From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: Help for using fonts Nupuram
Date: Fri, 23 Dec 2022 13:13:25 +0100 [thread overview]
Message-ID: <75795a0c-e8e6-83fb-6fe8-d8e7cd27c287@freedom.nl> (raw)
In-Reply-To: <16cf343f-58ee-91a7-a680-bfb5163f92c4@leliseron.org>
On 12/23/2022 12:00 PM, Alain Delmotte via ntg-context wrote:
> Hi!
>
> I am trying to run the example Hans published on the 1st of December
> with a new upload.
> It is about using the variable font Nupuram.
>
> I downloaded the font in a big .zip file.
> It contains: two explaining files and folder with sub-folder
> "Nupuram", which in turn contains 6 subsub-filders:
> - otf with 32 otf font files
> - otf-variable with 1 file "Nupuram-VF.otf"
> - ttf with 32 ttf font files
> - ttf-variable with 1 file "Nupuram-VF.ttf"
> - ufo with 32 subfolders xxx.ufo
> - webfonts with 33 xxx.woff2 files
>
> After looking to contextgarden,I tried to put the "Nupuram" sub-folder
> or only the folders with .otf in different places of my context-lmtx
> folder, and using "mtxrun --script font --reload".
> But the example of Hans didn't work.
>
> Then I install the .ttf font files in Windows\fonts; it works, but 1)
> trying to install the Nupuram-VF.ttf, I have the message that
> Nupuram-Regular is already installed; and 2) I get the font in the
> example, but no changes of width or colour.
>
> So, now I deleted all the Nupuram everywhere.
> How could I have it fully working under context-lmtx?
>
> I have different places for fonts in my context-lmtx:
> - tex\texmf\fonts mainly empty except \data
> - texmf-context\fonts populated
> - texmf-fonts empty
> - texmf-modules\fonts populated
don't mis instances and variable fonts here because they have clashing
(internal) names; put the variable fonts in:
fonts/data/nupuram/*
then run mtxrun --make
and see if s-fonts-variable.mk*v runs (check at the end what font is used)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-12-23 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 11:00 Alain Delmotte via ntg-context
2022-12-23 12:13 ` Hans Hagen via ntg-context [this message]
2022-12-23 12:13 ` Hans Hagen via ntg-context
2022-12-23 12:50 ` Pablo Rodriguez via ntg-context
2022-12-23 13:48 ` Pablo Rodriguez via ntg-context
2022-12-23 17:18 ` Alain Delmotte 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=75795a0c-e8e6-83fb-6fe8-d8e7cd27c287@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).