-
Notifications
You must be signed in to change notification settings - Fork 34
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
With Renderer=HarfBuzz, \fontname output has no quotes #525
Comments
EDIT. Only after posting I made the link with a problem I had encountered some time ago where I was forced to use here is the MWE. \documentclass{book}% no (immediate) problem with article class
\usepackage{fontspec}
\defaultfontfeatures{Renderer=HarfBuzz}
%\usepackage{luaotfload}% does not solve the problem anything
\setmainfont{TeX Gyre Termes}[% no issue with TeXGyreTermes
Numbers={OldStyle},%
]
\begin{document}
0123456789
\end{document}
% Local variables:
% TeX-engine: luatex
% End: One gets:
I am attaching the full log. |
@khaledhosny ouch, I should have minimally checked. Does look like a duplicate indeed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
With Renderer=HarfBuzz,
\fontname
output has no quotes.Check/indicate
Minimal example demonstrating the issue
Further details
I am using
\small
because without it, the second line in output ends withat 10pt
and I wanted to exclude that it may have to do with missing quotes.For background I hit againts this while updating a
mathastext
work-around to also take care ofRenderer=HarfBuzz
. Due to missing quotes, an error arose later when using the transmogrified output of\fontname
.edit: mathastext
1.4
soon to get released works around this at macro level.It may be that this has nothing to do with
fontspec
and does not belong here.However for non-expert the world of LuaLaTeX font is simply too complex to try to disentangle what belongs to fontspec, what belongs to luaotfload and what belongs to LuaTeX proper or perhaps again something else.
The text was updated successfully, but these errors were encountered: