From: Mohammad Hossein Bateni <bateni@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ttf font not seen ?
Date: Mon, 26 Aug 2019 15:27:58 -0400 [thread overview]
Message-ID: <CAMHZ1dbzcNQCmg_0U=Hi4ZtFgbuUyjKJa86eFGvN4b9_w=XgAA@mail.gmail.com> (raw)
In-Reply-To: <fc94c2c5-d233-2ba0-c5b3-0d52235690b7@klankschap.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2108 bytes --]
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.
On Mon, Aug 26, 2019 at 11:09 AM Floris van Manen <vm@klankschap.nl> wrote:
> using the latest context version luametatex on ubuntu 19.4
>
> system > ConTeXt ver: 2019.08.24 22:50 MKIV beta fmt:
> 2019.8.25 int: english/english
> system > 'cont-new.mkiv' loaded
>
>
> with the dijkstra.ttf font apparently seen:
>
> $ mtxrun --script fonts --list --all --name dijkstra
> identifier familyname fontname filename
> subfont instances
>
> dijkstra dijkstra dijkstra ~/.local/share/fonts/Unknown
> Vendor/TrueType/Dijkstra/Dijkstra_Thin.ttf
> dijkstranormal dijkstra dijkstra ~/.local/share/fonts/Unknown
> Vendor/TrueType/Dijkstra/Dijkstra_Thin.ttf
> dijkstraregular dijkstra dijkstra ~/.local/share/fonts/Unknown
> Vendor/TrueType/Dijkstra/Dijkstra_Thin.ttf
>
>
>
> context will complain that the font is unknown:
>
> selectfont > The requested font 'dijkstra' has no files for the
> 'tf' alternative, Latin Modern is used instead.
>
>
> I assume i missed a critical step somewhere down the road.
> any hints?
>
> thanks
> Floris
>
>
>
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 3208 bytes --]
[-- Attachment #2: 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 19:27 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 [this message]
2019-08-26 20:11 ` Floris van Manen
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='CAMHZ1dbzcNQCmg_0U=Hi4ZtFgbuUyjKJa86eFGvN4b9_w=XgAA@mail.gmail.com' \
--to=bateni@gmail.com \
--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).