Skip to content
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

Nested \mathcal in \mathrm fails #356

Closed
eg9 opened this issue Jun 7, 2016 · 3 comments
Closed

Nested \mathcal in \mathrm fails #356

eg9 opened this issue Jun 7, 2016 · 3 comments
Projects

Comments

@eg9
Copy link
Contributor

eg9 commented Jun 7, 2016

Compiling the following file with either XeLaTeX or LuaLaTeX, the calligraphic A doesn't show up:

\documentclass{article}
\usepackage{unicode-math}
\setmainfont{TeX Gyre Pagella}
\begin{document}
$A\mathrm{\mathcal{A}}A$
\end{document}

The log file shows

Missing character: There is no 𝒜 in font TeX Gyre Pagella/OT:script=latn;language=DFLT;mapping=tex-text;!

This can be solved by using \symrm instead of \mathrm, but it is a serious flaw nonetheless, because also \DeclareMathOperator{\foo}{A\mathcal{A}A} (after loading amsmath) fails in the same fashion.

If, instead, the text font is set before loading unicode-math, the issue doesn't show:

\documentclass{article}
\usepackage{fontspec}
\setmainfont{TeX Gyre Pagella}
\usepackage{unicode-math}
\begin{document}
$A\mathrm{\mathcal{A}}A$
\end{document}

Also \DeclareMathOperator works with this setup.

Reference: http://tex.stackexchange.com/q/313584/4427

@bodograumann
Copy link

This seems to be fixed in 2017/01/27 v0.8d. Similarly to my own problem. Though I would be interested what exactly the problem was and which commit fixed it.

@wspr wspr added this to For consideration in v0.9 Oct 23, 2017
@wspr
Copy link
Collaborator

wspr commented Jan 5, 2018

@canaaerus — the implementation of unicode-math is a bit tangled up... sometimes a fix in one area magically fixes other problems :) Glad to hear this has been resolved.

@wspr wspr closed this as completed Jan 5, 2018
v0.9 automation moved this from For consideration to Released Jan 5, 2018
@wspr
Copy link
Collaborator

wspr commented Jan 6, 2018

This doesn't actually seem to be fixed (any more, perhaps)…

@wspr wspr reopened this Jan 6, 2018
v0.9 automation moved this from Released to To Do Jan 6, 2018
wspr added a commit that referenced this issue Jan 6, 2018
@wspr wspr closed this as completed in 0f245c2 Feb 1, 2018
v0.9 automation moved this from To Do to Released Feb 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
v0.9
  
Released
Development

No branches or pull requests

3 participants