From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: LMTX and system fonts
Date: Sun, 28 Apr 2019 11:01:58 +0200 [thread overview]
Message-ID: <e0ca844f-76d4-fece-a752-e81dc5c88cc4@gmx.es> (raw)
In-Reply-To: <nycvar.YAK.7.76.44.1904271704240.29315@nqv-guvaxcnq>
On 4/27/19 11:06 PM, Aditya Mahajan wrote:
> On Sat, 27 Apr 2019, Pablo Rodriguez wrote:
>> [...]
>> If the soft symlink for the fonts directory is itself tex/texmf-fonts/,
>> ConTeXt LMTX handles the fonts right.
>
> The texmf-fonts directory must follow TDS (tex document structure).
> Assuming that ~/Documents/ousia-fonts simply contains a bunch of
> directories with opentype fonts...
It contains a bunch of fonts, no directory.
> I'd try symlinking it to
>
> tex/texmf-fonts/font/opentype/data
It doesn’t work.
Adding a link in tex/texmf-fonts/ for each font file is the only thing
that works fine.
And I wonder what may be wrong with the fonts from c:\windows\fonts\ not
being read in Win7.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2019-04-28 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 12:13 Pablo Rodriguez
2019-04-27 15:37 ` Hans Hagen
2019-04-27 16:25 ` Pablo Rodriguez
2019-04-27 16:35 ` Pablo Rodriguez
2019-04-27 17:36 ` Hans Hagen
2019-04-27 19:32 ` Pablo Rodriguez
2019-04-27 21:06 ` Aditya Mahajan
2019-04-28 9:01 ` Pablo Rodriguez [this message]
2019-04-27 19:50 ` Otared Kavian
2019-04-28 8:55 ` Pablo Rodriguez
2019-04-28 15:22 ` Alan Braslau
2019-05-01 11:07 ` Pablo Rodriguez
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=e0ca844f-76d4-fece-a752-e81dc5c88cc4@gmx.es \
--to=oinos@gmx.es \
--cc=ntg-context@ntg.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).