luajittex ignores fonts luatex findsSwitching To ConTeXt Minimals: Missing Last Step for MacTeX 2010Fatal...

Sometimes a banana is just a banana

I can't die. Who am I?

Where is the line between being obedient and getting bullied by a boss?

How can I be pwned if I'm not registered on the compromised site?

How can I create a Table like this in Latex?

Why doesn't Object.keys return a keyof type in TypeScript?

In Adventurer's League, is it possible to keep the Ring of Winter if you manage to acquire it in the Tomb of Annihilation adventure?

Achieving MPPT of a solar panel with LM2596

I encountered my boss during an on-site interview at another company. Should I bring it up when seeing him next time?

Do higher etale homotopy groups of spectrum of a field always vanish?

What is a term for a function that when called repeatedly, has the same effect as calling once?

Reason why dimensional travelling would be restricted

Inverse of the covariance matrix of a multivariate normal distribution

Toast materialize

Dystopian novel where telepathic humans live under a dome

What could trigger powerful quakes on icy world?

At what level can a party fight a mimic?

Where is the fallacy here?

Is divide-by-zero a security vulnerability?

Can a space-faring robot still function over a billion years?

Is there a legal poaching?

Woman in friend circle telling people I "should be fired"

Difference between 'stomach' and 'uterus'

Why do phishing e-mails use faked e-mail addresses instead of the real one?



luajittex ignores fonts luatex finds


Switching To ConTeXt Minimals: Missing Last Step for MacTeX 2010Fatal format file error; stymied. fmtutil: infinite recursionConTeXt keeps trying to create “missing” font filesWhen to use LuaJitTeX in favour of LuaTeX?Same mathematical fonts with LuaTeX and ConTeXtpdfcrop using luatex engine minimal setupLuaLaTeX: How to use a char directive inside a string.gsub function?Minimal ConTeXt and Husayni examplelualatex (with fontspec) finds fonts only by font file nameContext : How to install and use new opentype (math) fonts?













2















With LuajitTeX, Version 1.10.0 (TeX Live 2019) and ConTeXt ver: 2019.02.26 20:04 MKIV beta fmt: 2019.3.1 I can run the following MWE:



setupbodyfont[postscript,sans,12pt]
starttext
Test
stoptext


Adding % engine=luajittex at the top breaks everything:



$ context font.tex 
mtx-context | redirect texlua -> luajittex: luajittex --luaonly "/home/stenner/.local/bin/mtxrun" --script context font.tex --redirected
mtx-context | run 1: luajittex --fmt="$TEXDIR/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luajittex/cont-en" --jobname="font" --lua="$TEXDIR/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luajittex/cont-en.lui" --c:currentrun=1 --c:engine="luajittex" --c:fulljobname="./font.tex" --c:input="./font.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:redirected --c:texmfbinpath="$TEXDIR/bin/x86_64-linux" "cont-yes.mkiv"

This is LuajitTeX, Version 1.10.0 (TeX Live 2019)
system commands enabled.
open source > level 1, order 1, name '$TEXDIR/texmf-dist/tex/context/base/mkiv/cont-yes.mkiv'
system >
system > ConTeXt ver: 2019.02.26 20:04 MKIV beta fmt: 2019.3.1 int: english/english
system >
system > 'cont-new.mkiv' loaded
open source > level 2, order 2, name '$TEXDIR/texmf-dist/tex/context/base/mkiv/cont-new.mkiv'
system > beware: some patches loaded from cont-new.mkiv
close source > level 2, order 2, name '$TEXDIR/texmf-dist/tex/context/base/mkiv/cont-new.mkiv'
system > files > jobname 'font', input './font', result 'font'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 2, order 3, name '/tmp/font.tex'
open source > level 3, order 4, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-postscript.mkiv'
open source > level 4, order 5, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'
close source > level 4, order 5, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'
close source > level 3, order 5, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-postscript.mkiv'
fonts > defining > font with asked name 'texgyreheros-regular' is not found using lookup 'file'
fonts > defining > unknown font 'texgyreheros-regular', loading aborted
[snip]

fonts > !! No bodyfont has been defined and no defaults have been
fonts > !! loaded (maybe due to a missing starttext).


In theory, ConTeXt is able to find the font:



$ mtxrun --script fonts --list texgyreheros

identifier familyname fontname filename subfont instances

texgyreherosregular texgyreheros texgyreherosregular texgyreheros-regular.otf









share|improve this question




















  • 2





    For a context question the tag luaotfload is wrong.

    – Ulrike Fischer
    Mar 1 at 11:51











  • I cannot reproduce with latest beta. I'm also curious where you obtained this version of ConTeXt. My local version still reports This is LuajitTeX, Version 1.09.2 (TeX Live 2019/dev).

    – Henri Menke
    Mar 1 at 20:29






  • 2





    Could you try executing the following: context --make; contextjit --make; mtxrun --generate; mtxrunjit --generate. If that doesn't fix it, try additionally mtxrun --script fonts --reload; mtxrunjit --script fonts --reload.

    – Henri Menke
    Mar 1 at 20:36











  • @HenriMenke tlmgr info context reports it as context revision 50165. After rebuilding everything with mtxrunjit and using contextjit instead of the %% engine = luajittex comment it produced the same output as plain context

    – tstenner
    Mar 2 at 9:47






  • 1





    @tstenner So the problem is solved?

    – Henri Menke
    Mar 2 at 10:43
















2















With LuajitTeX, Version 1.10.0 (TeX Live 2019) and ConTeXt ver: 2019.02.26 20:04 MKIV beta fmt: 2019.3.1 I can run the following MWE:



setupbodyfont[postscript,sans,12pt]
starttext
Test
stoptext


Adding % engine=luajittex at the top breaks everything:



$ context font.tex 
mtx-context | redirect texlua -> luajittex: luajittex --luaonly "/home/stenner/.local/bin/mtxrun" --script context font.tex --redirected
mtx-context | run 1: luajittex --fmt="$TEXDIR/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luajittex/cont-en" --jobname="font" --lua="$TEXDIR/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luajittex/cont-en.lui" --c:currentrun=1 --c:engine="luajittex" --c:fulljobname="./font.tex" --c:input="./font.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:redirected --c:texmfbinpath="$TEXDIR/bin/x86_64-linux" "cont-yes.mkiv"

This is LuajitTeX, Version 1.10.0 (TeX Live 2019)
system commands enabled.
open source > level 1, order 1, name '$TEXDIR/texmf-dist/tex/context/base/mkiv/cont-yes.mkiv'
system >
system > ConTeXt ver: 2019.02.26 20:04 MKIV beta fmt: 2019.3.1 int: english/english
system >
system > 'cont-new.mkiv' loaded
open source > level 2, order 2, name '$TEXDIR/texmf-dist/tex/context/base/mkiv/cont-new.mkiv'
system > beware: some patches loaded from cont-new.mkiv
close source > level 2, order 2, name '$TEXDIR/texmf-dist/tex/context/base/mkiv/cont-new.mkiv'
system > files > jobname 'font', input './font', result 'font'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 2, order 3, name '/tmp/font.tex'
open source > level 3, order 4, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-postscript.mkiv'
open source > level 4, order 5, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'
close source > level 4, order 5, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'
close source > level 3, order 5, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-postscript.mkiv'
fonts > defining > font with asked name 'texgyreheros-regular' is not found using lookup 'file'
fonts > defining > unknown font 'texgyreheros-regular', loading aborted
[snip]

fonts > !! No bodyfont has been defined and no defaults have been
fonts > !! loaded (maybe due to a missing starttext).


In theory, ConTeXt is able to find the font:



$ mtxrun --script fonts --list texgyreheros

identifier familyname fontname filename subfont instances

texgyreherosregular texgyreheros texgyreherosregular texgyreheros-regular.otf









share|improve this question




















  • 2





    For a context question the tag luaotfload is wrong.

    – Ulrike Fischer
    Mar 1 at 11:51











  • I cannot reproduce with latest beta. I'm also curious where you obtained this version of ConTeXt. My local version still reports This is LuajitTeX, Version 1.09.2 (TeX Live 2019/dev).

    – Henri Menke
    Mar 1 at 20:29






  • 2





    Could you try executing the following: context --make; contextjit --make; mtxrun --generate; mtxrunjit --generate. If that doesn't fix it, try additionally mtxrun --script fonts --reload; mtxrunjit --script fonts --reload.

    – Henri Menke
    Mar 1 at 20:36











  • @HenriMenke tlmgr info context reports it as context revision 50165. After rebuilding everything with mtxrunjit and using contextjit instead of the %% engine = luajittex comment it produced the same output as plain context

    – tstenner
    Mar 2 at 9:47






  • 1





    @tstenner So the problem is solved?

    – Henri Menke
    Mar 2 at 10:43














2












2








2








With LuajitTeX, Version 1.10.0 (TeX Live 2019) and ConTeXt ver: 2019.02.26 20:04 MKIV beta fmt: 2019.3.1 I can run the following MWE:



setupbodyfont[postscript,sans,12pt]
starttext
Test
stoptext


Adding % engine=luajittex at the top breaks everything:



$ context font.tex 
mtx-context | redirect texlua -> luajittex: luajittex --luaonly "/home/stenner/.local/bin/mtxrun" --script context font.tex --redirected
mtx-context | run 1: luajittex --fmt="$TEXDIR/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luajittex/cont-en" --jobname="font" --lua="$TEXDIR/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luajittex/cont-en.lui" --c:currentrun=1 --c:engine="luajittex" --c:fulljobname="./font.tex" --c:input="./font.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:redirected --c:texmfbinpath="$TEXDIR/bin/x86_64-linux" "cont-yes.mkiv"

This is LuajitTeX, Version 1.10.0 (TeX Live 2019)
system commands enabled.
open source > level 1, order 1, name '$TEXDIR/texmf-dist/tex/context/base/mkiv/cont-yes.mkiv'
system >
system > ConTeXt ver: 2019.02.26 20:04 MKIV beta fmt: 2019.3.1 int: english/english
system >
system > 'cont-new.mkiv' loaded
open source > level 2, order 2, name '$TEXDIR/texmf-dist/tex/context/base/mkiv/cont-new.mkiv'
system > beware: some patches loaded from cont-new.mkiv
close source > level 2, order 2, name '$TEXDIR/texmf-dist/tex/context/base/mkiv/cont-new.mkiv'
system > files > jobname 'font', input './font', result 'font'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 2, order 3, name '/tmp/font.tex'
open source > level 3, order 4, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-postscript.mkiv'
open source > level 4, order 5, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'
close source > level 4, order 5, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'
close source > level 3, order 5, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-postscript.mkiv'
fonts > defining > font with asked name 'texgyreheros-regular' is not found using lookup 'file'
fonts > defining > unknown font 'texgyreheros-regular', loading aborted
[snip]

fonts > !! No bodyfont has been defined and no defaults have been
fonts > !! loaded (maybe due to a missing starttext).


In theory, ConTeXt is able to find the font:



$ mtxrun --script fonts --list texgyreheros

identifier familyname fontname filename subfont instances

texgyreherosregular texgyreheros texgyreherosregular texgyreheros-regular.otf









share|improve this question
















With LuajitTeX, Version 1.10.0 (TeX Live 2019) and ConTeXt ver: 2019.02.26 20:04 MKIV beta fmt: 2019.3.1 I can run the following MWE:



setupbodyfont[postscript,sans,12pt]
starttext
Test
stoptext


Adding % engine=luajittex at the top breaks everything:



$ context font.tex 
mtx-context | redirect texlua -> luajittex: luajittex --luaonly "/home/stenner/.local/bin/mtxrun" --script context font.tex --redirected
mtx-context | run 1: luajittex --fmt="$TEXDIR/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luajittex/cont-en" --jobname="font" --lua="$TEXDIR/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luajittex/cont-en.lui" --c:currentrun=1 --c:engine="luajittex" --c:fulljobname="./font.tex" --c:input="./font.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:redirected --c:texmfbinpath="$TEXDIR/bin/x86_64-linux" "cont-yes.mkiv"

This is LuajitTeX, Version 1.10.0 (TeX Live 2019)
system commands enabled.
open source > level 1, order 1, name '$TEXDIR/texmf-dist/tex/context/base/mkiv/cont-yes.mkiv'
system >
system > ConTeXt ver: 2019.02.26 20:04 MKIV beta fmt: 2019.3.1 int: english/english
system >
system > 'cont-new.mkiv' loaded
open source > level 2, order 2, name '$TEXDIR/texmf-dist/tex/context/base/mkiv/cont-new.mkiv'
system > beware: some patches loaded from cont-new.mkiv
close source > level 2, order 2, name '$TEXDIR/texmf-dist/tex/context/base/mkiv/cont-new.mkiv'
system > files > jobname 'font', input './font', result 'font'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 2, order 3, name '/tmp/font.tex'
open source > level 3, order 4, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-postscript.mkiv'
open source > level 4, order 5, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'
close source > level 4, order 5, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'
close source > level 3, order 5, name '$TEXDIR/texmf-dist/tex/context/fonts/mkiv/type-imp-postscript.mkiv'
fonts > defining > font with asked name 'texgyreheros-regular' is not found using lookup 'file'
fonts > defining > unknown font 'texgyreheros-regular', loading aborted
[snip]

fonts > !! No bodyfont has been defined and no defaults have been
fonts > !! loaded (maybe due to a missing starttext).


In theory, ConTeXt is able to find the font:



$ mtxrun --script fonts --list texgyreheros

identifier familyname fontname filename subfont instances

texgyreherosregular texgyreheros texgyreherosregular texgyreheros-regular.otf






luatex context






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 1 at 11:51









Ulrike Fischer

194k8302688




194k8302688










asked Mar 1 at 11:21









tstennertstenner

206110




206110








  • 2





    For a context question the tag luaotfload is wrong.

    – Ulrike Fischer
    Mar 1 at 11:51











  • I cannot reproduce with latest beta. I'm also curious where you obtained this version of ConTeXt. My local version still reports This is LuajitTeX, Version 1.09.2 (TeX Live 2019/dev).

    – Henri Menke
    Mar 1 at 20:29






  • 2





    Could you try executing the following: context --make; contextjit --make; mtxrun --generate; mtxrunjit --generate. If that doesn't fix it, try additionally mtxrun --script fonts --reload; mtxrunjit --script fonts --reload.

    – Henri Menke
    Mar 1 at 20:36











  • @HenriMenke tlmgr info context reports it as context revision 50165. After rebuilding everything with mtxrunjit and using contextjit instead of the %% engine = luajittex comment it produced the same output as plain context

    – tstenner
    Mar 2 at 9:47






  • 1





    @tstenner So the problem is solved?

    – Henri Menke
    Mar 2 at 10:43














  • 2





    For a context question the tag luaotfload is wrong.

    – Ulrike Fischer
    Mar 1 at 11:51











  • I cannot reproduce with latest beta. I'm also curious where you obtained this version of ConTeXt. My local version still reports This is LuajitTeX, Version 1.09.2 (TeX Live 2019/dev).

    – Henri Menke
    Mar 1 at 20:29






  • 2





    Could you try executing the following: context --make; contextjit --make; mtxrun --generate; mtxrunjit --generate. If that doesn't fix it, try additionally mtxrun --script fonts --reload; mtxrunjit --script fonts --reload.

    – Henri Menke
    Mar 1 at 20:36











  • @HenriMenke tlmgr info context reports it as context revision 50165. After rebuilding everything with mtxrunjit and using contextjit instead of the %% engine = luajittex comment it produced the same output as plain context

    – tstenner
    Mar 2 at 9:47






  • 1





    @tstenner So the problem is solved?

    – Henri Menke
    Mar 2 at 10:43








2




2





For a context question the tag luaotfload is wrong.

– Ulrike Fischer
Mar 1 at 11:51





For a context question the tag luaotfload is wrong.

– Ulrike Fischer
Mar 1 at 11:51













I cannot reproduce with latest beta. I'm also curious where you obtained this version of ConTeXt. My local version still reports This is LuajitTeX, Version 1.09.2 (TeX Live 2019/dev).

– Henri Menke
Mar 1 at 20:29





I cannot reproduce with latest beta. I'm also curious where you obtained this version of ConTeXt. My local version still reports This is LuajitTeX, Version 1.09.2 (TeX Live 2019/dev).

– Henri Menke
Mar 1 at 20:29




2




2





Could you try executing the following: context --make; contextjit --make; mtxrun --generate; mtxrunjit --generate. If that doesn't fix it, try additionally mtxrun --script fonts --reload; mtxrunjit --script fonts --reload.

– Henri Menke
Mar 1 at 20:36





Could you try executing the following: context --make; contextjit --make; mtxrun --generate; mtxrunjit --generate. If that doesn't fix it, try additionally mtxrun --script fonts --reload; mtxrunjit --script fonts --reload.

– Henri Menke
Mar 1 at 20:36













@HenriMenke tlmgr info context reports it as context revision 50165. After rebuilding everything with mtxrunjit and using contextjit instead of the %% engine = luajittex comment it produced the same output as plain context

– tstenner
Mar 2 at 9:47





@HenriMenke tlmgr info context reports it as context revision 50165. After rebuilding everything with mtxrunjit and using contextjit instead of the %% engine = luajittex comment it produced the same output as plain context

– tstenner
Mar 2 at 9:47




1




1





@tstenner So the problem is solved?

– Henri Menke
Mar 2 at 10:43





@tstenner So the problem is solved?

– Henri Menke
Mar 2 at 10:43










1 Answer
1






active

oldest

votes


















1














In general, when ConTeXt can't find files which you are sure are there, or complains about undefined control sequences which you are sure are defined, or chokes on mismatched formats, try rebuilding the ConTeXt formats and caches:



# Remake the formats
context --make
contextjit --make
# Regenerate the file database
mtxrun --generate
mtxrunjit --generate


If you are loading fonts by fontname, rather than by filename (e.g. TeX Gyre Heros rather than texgyreheros-regular.otf) you should also reload the font database:



mtxrun --script fonts --reload
mtxrunjit --script fonts --reload





share|improve this answer
























  • Actually reloading the file and font database with both mtxrun and mtxrunjit might be unnecessary. It's probably sufficient to just use one of them, but I haven't tried.

    – Henri Menke
    yesterday











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f477273%2fluajittex-ignores-fonts-luatex-finds%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














In general, when ConTeXt can't find files which you are sure are there, or complains about undefined control sequences which you are sure are defined, or chokes on mismatched formats, try rebuilding the ConTeXt formats and caches:



# Remake the formats
context --make
contextjit --make
# Regenerate the file database
mtxrun --generate
mtxrunjit --generate


If you are loading fonts by fontname, rather than by filename (e.g. TeX Gyre Heros rather than texgyreheros-regular.otf) you should also reload the font database:



mtxrun --script fonts --reload
mtxrunjit --script fonts --reload





share|improve this answer
























  • Actually reloading the file and font database with both mtxrun and mtxrunjit might be unnecessary. It's probably sufficient to just use one of them, but I haven't tried.

    – Henri Menke
    yesterday
















1














In general, when ConTeXt can't find files which you are sure are there, or complains about undefined control sequences which you are sure are defined, or chokes on mismatched formats, try rebuilding the ConTeXt formats and caches:



# Remake the formats
context --make
contextjit --make
# Regenerate the file database
mtxrun --generate
mtxrunjit --generate


If you are loading fonts by fontname, rather than by filename (e.g. TeX Gyre Heros rather than texgyreheros-regular.otf) you should also reload the font database:



mtxrun --script fonts --reload
mtxrunjit --script fonts --reload





share|improve this answer
























  • Actually reloading the file and font database with both mtxrun and mtxrunjit might be unnecessary. It's probably sufficient to just use one of them, but I haven't tried.

    – Henri Menke
    yesterday














1












1








1







In general, when ConTeXt can't find files which you are sure are there, or complains about undefined control sequences which you are sure are defined, or chokes on mismatched formats, try rebuilding the ConTeXt formats and caches:



# Remake the formats
context --make
contextjit --make
# Regenerate the file database
mtxrun --generate
mtxrunjit --generate


If you are loading fonts by fontname, rather than by filename (e.g. TeX Gyre Heros rather than texgyreheros-regular.otf) you should also reload the font database:



mtxrun --script fonts --reload
mtxrunjit --script fonts --reload





share|improve this answer













In general, when ConTeXt can't find files which you are sure are there, or complains about undefined control sequences which you are sure are defined, or chokes on mismatched formats, try rebuilding the ConTeXt formats and caches:



# Remake the formats
context --make
contextjit --make
# Regenerate the file database
mtxrun --generate
mtxrunjit --generate


If you are loading fonts by fontname, rather than by filename (e.g. TeX Gyre Heros rather than texgyreheros-regular.otf) you should also reload the font database:



mtxrun --script fonts --reload
mtxrunjit --script fonts --reload






share|improve this answer












share|improve this answer



share|improve this answer










answered yesterday









Henri MenkeHenri Menke

76.1k8167281




76.1k8167281













  • Actually reloading the file and font database with both mtxrun and mtxrunjit might be unnecessary. It's probably sufficient to just use one of them, but I haven't tried.

    – Henri Menke
    yesterday



















  • Actually reloading the file and font database with both mtxrun and mtxrunjit might be unnecessary. It's probably sufficient to just use one of them, but I haven't tried.

    – Henri Menke
    yesterday

















Actually reloading the file and font database with both mtxrun and mtxrunjit might be unnecessary. It's probably sufficient to just use one of them, but I haven't tried.

– Henri Menke
yesterday





Actually reloading the file and font database with both mtxrun and mtxrunjit might be unnecessary. It's probably sufficient to just use one of them, but I haven't tried.

– Henri Menke
yesterday


















draft saved

draft discarded




















































Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f477273%2fluajittex-ignores-fonts-luatex-finds%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

El tren de la libertad Índice Antecedentes "Porque yo decido" Desarrollo de la...

Castillo d'Acher Características Menú de navegación

Connecting two nodes from the same mother node horizontallyTikZ: What EXACTLY does the the |- notation for...