Package fontspec Error: The font cannot be found on win10Adobe Garamond Pro not working with XeLaTeXAdobe...

What happens if I start too many background jobs?

Disabling Resource Governor in SQL Server

Which skill should be used for secret doors or traps: Perception or Investigation?

How to creep the reader out with what seems like a normal person?

Visa for volunteering in England

Binary Numbers Magic Trick

Copy line and insert it in a new position with sed or awk

Why is the SNP putting so much emphasis on currency plans?

Why do computer-science majors learn calculus?

Is it always OK to ask for a copy of the lecturer's slides?

Can I use 1000v rectifier diodes instead of 600v rectifier diodes?

Stark VS Thanos

How to scale a verbatim environment on a minipage?

Was Unix ever a single-user OS?

Applying a function to a nested list

Save terminal output to a txt file

Why debootstrap can only run as root?

Packet sniffer for MacOS Mojave and above

How do you center multiple equations that have multiple steps?

Why is Arya visibly scared in the library in S8E3?

CRT Oscilloscope - part of the plot is missing

Pressure to defend the relevance of one's area of mathematics

Why is Thanos so tough at the beginning of "Avengers: Endgame"?

If Melisandre foresaw another character closing blue eyes, why did she follow Stannis?



Package fontspec Error: The font cannot be found on win10


Adobe Garamond Pro not working with XeLaTeXAdobe Garamond Pro (otf) with mathdesignUsing a handwriting font from myscriptfont.comfontspec: Configuring project-local opticals fontfontspec error: “font-not-found”Minimal XeTeX distribution for Linuxfontspec font-not-found / Invalid fontname on Mac updateHow are font names chosen for LuaLaTeX and XeLaTeX?Who changed my Chinese character?













1















I have installed the Adobe Garamond Pro.otf fonts on my computer running win10, as shown in the following picture.
enter image description here



However, when I run xelatex, the otf fonts cannot be found.



Here is an example:



documentclass[a4paper,11pt]{article}

usepackage[CJKchecksingle,CJKnumber]{xeCJK}
setmainfont[Mapping=tex-text]{Adobe Garamond Pro}

begin{document}

test test test

end{document}









share|improve this question























  • BTW, the "fc-list" command cannot found the oft fonts.

    – On1gub
    Jan 28 at 17:05











  • First try running fc-cache.

    – Davislor
    Jan 28 at 17:06
















1















I have installed the Adobe Garamond Pro.otf fonts on my computer running win10, as shown in the following picture.
enter image description here



However, when I run xelatex, the otf fonts cannot be found.



Here is an example:



documentclass[a4paper,11pt]{article}

usepackage[CJKchecksingle,CJKnumber]{xeCJK}
setmainfont[Mapping=tex-text]{Adobe Garamond Pro}

begin{document}

test test test

end{document}









share|improve this question























  • BTW, the "fc-list" command cannot found the oft fonts.

    – On1gub
    Jan 28 at 17:05











  • First try running fc-cache.

    – Davislor
    Jan 28 at 17:06














1












1








1


0






I have installed the Adobe Garamond Pro.otf fonts on my computer running win10, as shown in the following picture.
enter image description here



However, when I run xelatex, the otf fonts cannot be found.



Here is an example:



documentclass[a4paper,11pt]{article}

usepackage[CJKchecksingle,CJKnumber]{xeCJK}
setmainfont[Mapping=tex-text]{Adobe Garamond Pro}

begin{document}

test test test

end{document}









share|improve this question














I have installed the Adobe Garamond Pro.otf fonts on my computer running win10, as shown in the following picture.
enter image description here



However, when I run xelatex, the otf fonts cannot be found.



Here is an example:



documentclass[a4paper,11pt]{article}

usepackage[CJKchecksingle,CJKnumber]{xeCJK}
setmainfont[Mapping=tex-text]{Adobe Garamond Pro}

begin{document}

test test test

end{document}






xetex fontspec






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 28 at 16:44









On1gubOn1gub

82




82













  • BTW, the "fc-list" command cannot found the oft fonts.

    – On1gub
    Jan 28 at 17:05











  • First try running fc-cache.

    – Davislor
    Jan 28 at 17:06



















  • BTW, the "fc-list" command cannot found the oft fonts.

    – On1gub
    Jan 28 at 17:05











  • First try running fc-cache.

    – Davislor
    Jan 28 at 17:06

















BTW, the "fc-list" command cannot found the oft fonts.

– On1gub
Jan 28 at 17:05





BTW, the "fc-list" command cannot found the oft fonts.

– On1gub
Jan 28 at 17:05













First try running fc-cache.

– Davislor
Jan 28 at 17:06





First try running fc-cache.

– Davislor
Jan 28 at 17:06










2 Answers
2






active

oldest

votes


















0














First, try running fc-cache.



If that doesn’t work, setmainfont{[Adobe Garamond Pro]} or the family name reported by otfinfo might.



Loading a font by display name is no longer the preferred way, though, and you can instead try loading by filename. That is, load the actual filenames you get when you dir C:WindowsFontsAdobe*.otf, with options such as UprightFont = *-Regular, ItalicFont = *-Italic and so on.



Although that isn’t the problem in this case, that is the only way to load a font in XeTeX that is installed as part of the TeX distribution, rather than as a system font.






share|improve this answer


























  • Why do you say that ‘Loading a font by display name is now deprecated’? I don’t see anything about that in the documentation.

    – Thérèse
    Jan 28 at 17:36











  • @Thérèse youtube.com/watch?v=L0MfY6EkiKc

    – Davislor
    Jan 28 at 17:39








  • 2





    Yikes! texdoc youtube? Thanks for the link.

    – Thérèse
    Jan 28 at 17:41











  • @Thérèse I rephrased that sentence. Thanks for pointing it out.

    – Davislor
    Jan 28 at 17:45











  • @Thérèse The manual does say that loading by file name is the only way for XeTeX to see a font installed in a TeX, rather than a system, directory.

    – Davislor
    Jan 28 at 19:03



















0














Same problem and solved, win10



DONOT double click to install, it will install this font for current user.



right click the font file, choose install for all users



enter image description here



There are two path,C:WindowsFonts and C:Usersuser_nameAppDataLocalMicrosoftWindowsFonts,



install for all users will install the font file in first path, and show it in first path, double click will install the font file in second path, but show it in first path. This will mislead you.






share|improve this answer








New contributor




Bluedrops is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Welcome to TeX.SE!

    – Kurt
    50 mins ago












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%2f472262%2fpackage-fontspec-error-the-font-cannot-be-found-on-win10%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














First, try running fc-cache.



If that doesn’t work, setmainfont{[Adobe Garamond Pro]} or the family name reported by otfinfo might.



Loading a font by display name is no longer the preferred way, though, and you can instead try loading by filename. That is, load the actual filenames you get when you dir C:WindowsFontsAdobe*.otf, with options such as UprightFont = *-Regular, ItalicFont = *-Italic and so on.



Although that isn’t the problem in this case, that is the only way to load a font in XeTeX that is installed as part of the TeX distribution, rather than as a system font.






share|improve this answer


























  • Why do you say that ‘Loading a font by display name is now deprecated’? I don’t see anything about that in the documentation.

    – Thérèse
    Jan 28 at 17:36











  • @Thérèse youtube.com/watch?v=L0MfY6EkiKc

    – Davislor
    Jan 28 at 17:39








  • 2





    Yikes! texdoc youtube? Thanks for the link.

    – Thérèse
    Jan 28 at 17:41











  • @Thérèse I rephrased that sentence. Thanks for pointing it out.

    – Davislor
    Jan 28 at 17:45











  • @Thérèse The manual does say that loading by file name is the only way for XeTeX to see a font installed in a TeX, rather than a system, directory.

    – Davislor
    Jan 28 at 19:03
















0














First, try running fc-cache.



If that doesn’t work, setmainfont{[Adobe Garamond Pro]} or the family name reported by otfinfo might.



Loading a font by display name is no longer the preferred way, though, and you can instead try loading by filename. That is, load the actual filenames you get when you dir C:WindowsFontsAdobe*.otf, with options such as UprightFont = *-Regular, ItalicFont = *-Italic and so on.



Although that isn’t the problem in this case, that is the only way to load a font in XeTeX that is installed as part of the TeX distribution, rather than as a system font.






share|improve this answer


























  • Why do you say that ‘Loading a font by display name is now deprecated’? I don’t see anything about that in the documentation.

    – Thérèse
    Jan 28 at 17:36











  • @Thérèse youtube.com/watch?v=L0MfY6EkiKc

    – Davislor
    Jan 28 at 17:39








  • 2





    Yikes! texdoc youtube? Thanks for the link.

    – Thérèse
    Jan 28 at 17:41











  • @Thérèse I rephrased that sentence. Thanks for pointing it out.

    – Davislor
    Jan 28 at 17:45











  • @Thérèse The manual does say that loading by file name is the only way for XeTeX to see a font installed in a TeX, rather than a system, directory.

    – Davislor
    Jan 28 at 19:03














0












0








0







First, try running fc-cache.



If that doesn’t work, setmainfont{[Adobe Garamond Pro]} or the family name reported by otfinfo might.



Loading a font by display name is no longer the preferred way, though, and you can instead try loading by filename. That is, load the actual filenames you get when you dir C:WindowsFontsAdobe*.otf, with options such as UprightFont = *-Regular, ItalicFont = *-Italic and so on.



Although that isn’t the problem in this case, that is the only way to load a font in XeTeX that is installed as part of the TeX distribution, rather than as a system font.






share|improve this answer















First, try running fc-cache.



If that doesn’t work, setmainfont{[Adobe Garamond Pro]} or the family name reported by otfinfo might.



Loading a font by display name is no longer the preferred way, though, and you can instead try loading by filename. That is, load the actual filenames you get when you dir C:WindowsFontsAdobe*.otf, with options such as UprightFont = *-Regular, ItalicFont = *-Italic and so on.



Although that isn’t the problem in this case, that is the only way to load a font in XeTeX that is installed as part of the TeX distribution, rather than as a system font.







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 28 at 19:07

























answered Jan 28 at 17:15









DavislorDavislor

7,6791433




7,6791433













  • Why do you say that ‘Loading a font by display name is now deprecated’? I don’t see anything about that in the documentation.

    – Thérèse
    Jan 28 at 17:36











  • @Thérèse youtube.com/watch?v=L0MfY6EkiKc

    – Davislor
    Jan 28 at 17:39








  • 2





    Yikes! texdoc youtube? Thanks for the link.

    – Thérèse
    Jan 28 at 17:41











  • @Thérèse I rephrased that sentence. Thanks for pointing it out.

    – Davislor
    Jan 28 at 17:45











  • @Thérèse The manual does say that loading by file name is the only way for XeTeX to see a font installed in a TeX, rather than a system, directory.

    – Davislor
    Jan 28 at 19:03



















  • Why do you say that ‘Loading a font by display name is now deprecated’? I don’t see anything about that in the documentation.

    – Thérèse
    Jan 28 at 17:36











  • @Thérèse youtube.com/watch?v=L0MfY6EkiKc

    – Davislor
    Jan 28 at 17:39








  • 2





    Yikes! texdoc youtube? Thanks for the link.

    – Thérèse
    Jan 28 at 17:41











  • @Thérèse I rephrased that sentence. Thanks for pointing it out.

    – Davislor
    Jan 28 at 17:45











  • @Thérèse The manual does say that loading by file name is the only way for XeTeX to see a font installed in a TeX, rather than a system, directory.

    – Davislor
    Jan 28 at 19:03

















Why do you say that ‘Loading a font by display name is now deprecated’? I don’t see anything about that in the documentation.

– Thérèse
Jan 28 at 17:36





Why do you say that ‘Loading a font by display name is now deprecated’? I don’t see anything about that in the documentation.

– Thérèse
Jan 28 at 17:36













@Thérèse youtube.com/watch?v=L0MfY6EkiKc

– Davislor
Jan 28 at 17:39







@Thérèse youtube.com/watch?v=L0MfY6EkiKc

– Davislor
Jan 28 at 17:39






2




2





Yikes! texdoc youtube? Thanks for the link.

– Thérèse
Jan 28 at 17:41





Yikes! texdoc youtube? Thanks for the link.

– Thérèse
Jan 28 at 17:41













@Thérèse I rephrased that sentence. Thanks for pointing it out.

– Davislor
Jan 28 at 17:45





@Thérèse I rephrased that sentence. Thanks for pointing it out.

– Davislor
Jan 28 at 17:45













@Thérèse The manual does say that loading by file name is the only way for XeTeX to see a font installed in a TeX, rather than a system, directory.

– Davislor
Jan 28 at 19:03





@Thérèse The manual does say that loading by file name is the only way for XeTeX to see a font installed in a TeX, rather than a system, directory.

– Davislor
Jan 28 at 19:03











0














Same problem and solved, win10



DONOT double click to install, it will install this font for current user.



right click the font file, choose install for all users



enter image description here



There are two path,C:WindowsFonts and C:Usersuser_nameAppDataLocalMicrosoftWindowsFonts,



install for all users will install the font file in first path, and show it in first path, double click will install the font file in second path, but show it in first path. This will mislead you.






share|improve this answer








New contributor




Bluedrops is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Welcome to TeX.SE!

    – Kurt
    50 mins ago
















0














Same problem and solved, win10



DONOT double click to install, it will install this font for current user.



right click the font file, choose install for all users



enter image description here



There are two path,C:WindowsFonts and C:Usersuser_nameAppDataLocalMicrosoftWindowsFonts,



install for all users will install the font file in first path, and show it in first path, double click will install the font file in second path, but show it in first path. This will mislead you.






share|improve this answer








New contributor




Bluedrops is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Welcome to TeX.SE!

    – Kurt
    50 mins ago














0












0








0







Same problem and solved, win10



DONOT double click to install, it will install this font for current user.



right click the font file, choose install for all users



enter image description here



There are two path,C:WindowsFonts and C:Usersuser_nameAppDataLocalMicrosoftWindowsFonts,



install for all users will install the font file in first path, and show it in first path, double click will install the font file in second path, but show it in first path. This will mislead you.






share|improve this answer








New contributor




Bluedrops is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.










Same problem and solved, win10



DONOT double click to install, it will install this font for current user.



right click the font file, choose install for all users



enter image description here



There are two path,C:WindowsFonts and C:Usersuser_nameAppDataLocalMicrosoftWindowsFonts,



install for all users will install the font file in first path, and show it in first path, double click will install the font file in second path, but show it in first path. This will mislead you.







share|improve this answer








New contributor




Bluedrops is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this answer



share|improve this answer






New contributor




Bluedrops is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









answered 1 hour ago









BluedropsBluedrops

11




11




New contributor




Bluedrops is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Bluedrops is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Bluedrops is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • Welcome to TeX.SE!

    – Kurt
    50 mins ago



















  • Welcome to TeX.SE!

    – Kurt
    50 mins ago

















Welcome to TeX.SE!

– Kurt
50 mins ago





Welcome to TeX.SE!

– Kurt
50 mins ago


















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%2f472262%2fpackage-fontspec-error-the-font-cannot-be-found-on-win10%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...