fontspecluatexxetex
With \usepackage{fontspec}, \hbar does not show up correctly. Tested on LaTeX2e <2018-04-01> patch level 5 and fontspec.sty 2018/07/30 vv2.6h.
\documentclass{article}
\usepackage{fontspec}
\begin{document}
[$\hbar$]
\end{document}
With LuaLaTeX:
With XeLaTeX:
I found that
\usepackage{unicode-math}or
\usepackage[no-math]{fontspec}can resolve this problem, but I'm not sure which is better.
One reason to rely on fontspec over luainputenc comes from the package documentation of the second package. The abstract says simply:
Input encoding management for LuaTeX, needed only for compatibility with old documents. For new documents, using UTF-8 encoding and Unicode fonts is strongly recommended. You’ve been warned!
Then, the first section of the document, entitled "Overview: When (not) to use this package" reads:
This package is strictly meant for compatibility. It is usefull [sic] in the two (overlapping) following cases:
- Your source is not encoded in UTF-8 and you don’t want to reencode it for some reason.
- Your document is using legacy 8-bit fonts (with fontenc), as opposed to modern Unicode fonts (most probably with fontspec or luaotfload and fontenc with option EU2).
The same section then continues (in part):
luainputenc has several modes of operation. By default, it basically turns LuaTEX into an 8-bit engine, which means you loose half of the benefits from using LuaTEX.
In any event, I think it is fairly clear that, as the author of the package himself does not recommend using luainputenc for "new" documents, there is little reason for others to recommend it to other users. It does not seem to be recommended for the purpose you are using the package. (Which is perhaps fine: you have taken the time to explore what best suits your needs.)
Of course, one may choose to use this package over fontspec (I wish LuaTeX-based documents compiled more quickly, too!), but it seems a stretch to say that fontspec (or luaotfload) should not be recommended---especially to new users---before luainputenc. I am certainly not inclined to do so.
The fonts have a strange naming scheme. Call them explicitly.
\documentclass{article}
\usepackage{fontspec}
\setmonofont{JuliaMono}[
Extension=.ttf,
UprightFont=*-Regular,
BoldFont=*-Bold,
ItalicFont=*-RegularItalic,
BoldItalicFont=*-BoldItalic,
]
\begin{document}
\ttfamily α β δ σ π γ ϵ ε η ς θ ϑ ϕ φ ψ ά έ ή ί ό ύ ώ
\end{document}
Best Answer
The definition of hbar is quite encoding dependant. As fontspec changes the operator font it breaks.
You could redefine it if you don't want to switch to unicode-math: