Skip to content

luaotfload complains about not finding a file with an absolute path #527

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
3 of 4 tasks
avidseeker opened this issue Jul 20, 2024 · 4 comments
Closed
3 of 4 tasks

Comments

@avidseeker
Copy link

Description

Title.

Check/indicate

  • Relevant for XeTeX
  • Relevant for LuaTeX
  • Issue tracker has been searched for similar issues?
  • Links to <tex.stackexchange.com> discussion if appropriate

Minimal example demonstrating the issue

\documentclass[mla8]{mla}
\usepackage{fontspec}
\setmainfont{FreeSerif}
\fontspec{NotoColorEmoji}[
	Extension=.ttf,
	Path=/usr/share/texmf-dist/fonts/truetype/google/noto-emoji/,
	RawFeature={mode=harf}
]
\setmainfont{NotoColorEmoji}
\setmainfont[Script=Arabic]{ScheherazadeNew}

\begin{document}
\begin{paper}
🤔
\end{paper}
\end{document}

Checking luaotftool:

$ luaotfload-tool --find="Noto Color Emoji"
luaotfload | resolve : Font "Noto Color Emoji" found!
luaotfload | resolve : Resolved file name "/usr/share/texmf-dist/fonts/truetype/google/noto-emoji/NotoColorEmoji.ttf"

However, using lualatex to compile the document:

...
luaotfload | db : Reload initiated (formats: otf,ttf,ttc); reason: File not found: "NotoColorEmoji.otf".

luaotfload doesn't complain when documentclass is article. I tried checking what could be the potential problem with mla.cls, but it doesn't seem to tweak anything about fonts.

Further details

@wspr
Copy link
Collaborator

wspr commented Jul 21, 2024

Looking at the answer by egreg: https://tex.stackexchange.com/a/722870/179

This is an error with an external font package which is loaded by mla. What could fontspec do to improve this?

@avidseeker
Copy link
Author

Sorry, I submitted this issue before I found out the answer.

@wspr
Copy link
Collaborator

wspr commented Jul 21, 2024

@eg9 — do you think it would be reasonable for fontspec to add a global end package hook to clear the default font features? Document that should be a user feature only.

If so, could consider adding a \globalfontfeatures option as well which behaves in the current “unsafe” manner

@wspr
Copy link
Collaborator

wspr commented Jul 21, 2024

@avidseeker — no worries at all, thanks for filing bugs about it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants