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
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
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
___________________________________________________________________________________
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
On 26-08-19 22:11, Floris van Manen wrote:
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 ?
Is there a description available as how to include all font paths of the underlaying system (ubuntu) into the font awareness of the new luametatex system so they can be used? Apparently there is a difference between the older (works) and the newer (does not work) system. thanks Floris
participants (2)
-
Floris van Manen -
Mohammad Hossein Bateni