From: Floris van Manen <vm@klankschap.nl>
To: ntg-context@ntg.nl
Subject: Re: ttf font not seen ?
Date: Mon, 26 Aug 2019 22:11:13 +0200 [thread overview]
Message-ID: <e291c15b-93b3-ae3e-29ff-f79ae44c95cd@klankschap.nl> (raw)
In-Reply-To: <CAMHZ1dbzcNQCmg_0U=Hi4ZtFgbuUyjKJa86eFGvN4b9_w=XgAA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
On 26-08-19 21:27, Mohammad Hossein Bateni wrote:
> I have had the same problem. Unlike Mark IV Context, LMTX does not seem
> to recognize fonts outside its tree. Maybe there's some option to tweak
> with.
>
> The workaround I found was to copy the TTF files under
> "{context-lmtx-root}/tex/texmf/fonts/truetype/public/" and run "context
> --generate".
>
> If you like to have mtxrun font commands to work properly, you need to
> invoke "mtxrun --script font --reload" after that.
>
> Hope this helps.
nope.
does not work here.
can the native font paths be symbolically linked into the lmtx font tree ?
.F
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 2497 bytes --]
[-- Attachment #3: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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-08-26 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 15:06 Floris van Manen
2019-08-26 19:27 ` Mohammad Hossein Bateni
2019-08-26 20:11 ` Floris van Manen [this message]
2019-08-28 19:49 ` Floris van Manen
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=e291c15b-93b3-ae3e-29ff-f79ae44c95cd@klankschap.nl \
--to=vm@klankschap.nl \
--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).