4

Using LuaLaTeX and MinionPro (the one from Adobe Reader), I apparently cannot print the characters ϱ and ɔ ("symbolic rho" and "open o"). This I find a bit strange in a professional font. Can that really be true?

If you want a MWE so badly, here it is:

\documentclass{memoir}

\usepackage{fontspec}

\setmainfont[Ligatures={Common}]{Minion Pro}

\begin{document}
    Hellɔ woϱld.
\end{document}

I know I can do something like

\usepackage{newunicodechar}
\newunicodechar{ɔ}{\rotatebox[origin=c]{180}{c}}
\newunicodechar{ϱ}{ρ}

but is that really the way to do it? I especially don't like the first one. And the second one changes from one version of rho to another, which I would have liked to avoid.

Gaussler
  • 12,801
  • 2
    Thanks for the MWE (yeah, we always need it... Would be even better with article class and no font options). I do not have this font. Please try \symbol{"03F1}\symbol{"0254}. If there is nothing appearing, I would say, those symbols are not in Minion Pro. – LaRiFaRi Jan 23 '15 at 08:30
  • Nothing appearing, unfortunately. – Gaussler Jan 23 '15 at 08:31
  • 2
    Neither of the is a 'common' symbol (the rho here isn't the usual lower case Greek letter): it would not surprise me at all if they are lacking. A definitive check can be made using a font editor if you have access to the font files (I don't). – Joseph Wright Jan 23 '15 at 08:33
  • 1
    On the type tester of this page: https://typekit.com/fonts/minion-pro it looks like they are existing. What did you mean by "from Adobe Reader"? Did you buy the font package or do you use something shipped with Adobe Reader. Could be a minor bundle. If you are on Windows, install NexusFont and have a look on the files you have. – LaRiFaRi Jan 23 '15 at 08:42
  • Yes, I'm using a (perhaps limited?) copy of MinionPro that comes with Adobe Reader. – Gaussler Jan 23 '15 at 08:45
  • store1.adobe doesn't show the symbols. – Johannes_B Jan 23 '15 at 09:01
  • https://typekit.com/fonts/minion-pro does if I copy it into the "type tester". This shows that the characters do indeed exist in the paid version of the font. – Gaussler Jan 23 '15 at 09:04
  • 1
    @Gaussler At least to me, they are in a different font. I mean, it's obvious those characters are not from Minion Pro. – Manuel Jan 23 '15 at 09:09
  • 2
    I have the paid version, and these characters do not exist in this font (checked with Nexus Font). – Bernard Jan 23 '15 at 09:45
  • 1
    @Gaussler The font store of Adobe shows that the glyphs are non existing, if you zoom in on the typekit output you linked above, you will notice that the glyphs are taken from another font. – Johannes_B Jan 23 '15 at 14:26
  • 2
    @Gaussler I suggest one solution here: http://tex.stackexchange.com/questions/224584/define-fallback-font-for-specific-unicode-characters-in-lualatex – musarithmia Jan 23 '15 at 15:05

1 Answers1

4

The MinionPro font that comes with Adobe Reader does not have these symbols:

enter image description hereenter image description here

In short, you can't use characters from a font that doesn't have those characters. This is therefore not a question about TeX, and you seem to acknowledge that in your question, asking if it "can really be true" that Adobe's MinionPro font doesn't have these symbols. I'm therefore voting to close this question.

Sverre
  • 20,729
  • My question was meant to be about TeX. For --- since I simply didn't believe that those characters were not a part of a font as compatible as MinionPro --- I assumed that the error occurred on the TeX level. This turned out not to be the case; but that I could not have known until I asked the question. – Gaussler Jan 23 '15 at 19:43
  • In short: What the answer is about is not necessarily the same as what the question is about. – Gaussler Jan 23 '15 at 19:43
  • 2
    @Gaussler There's no real disagreement between us, so I see no need to pursue this further. You suspected in your question that either: (1) the font you were using didn't have the characters you needed. I confirmed this. Or: (2) Something's up with TeX. But there's not. This doesn't mean that there was anything wrong with your question (closing a question doesn't imply that). It was closed because the problem doesn't have anything to do with TeX. – Sverre Jan 23 '15 at 21:34