TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

If I compile the following minimal code with LuaLaTeX I seem to get a faulty pdf:

\setmainfont{Times New Roman}


If I open the resulting pdf-file in Adobe Acrobat and try to export it as a Word Document I an told that this is a bad pdf because of a "bad Type0 font":

Abobe Acrobat Export error message

Is it me who is doing something wrong or LuaLaTeX? Or fontspec? (The Font I'm using is the OpenType Times New Roman that comes with Windows7.)

Update: The problem also occurs with \setmainfont{Minion Pro}, but the error message is slightly different: Instead of "bad Type0 font" it says "cannot find CMap resource file".

share|improve this question

closed as off-topic by Joseph Wright Aug 3 '14 at 10:29

  • This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

Is the example really minimal in the sense that the error goes away if you remove [Ligatures=TeX]? Does the error occur with other fonts? Do you get errors from other software that reads pdfs? Are you not able to post the pdf for others to look at because it's not legal to redistribute the font? – Ben Crowell Mar 17 '13 at 5:17
I'm able to reproduce the problem. @BenCrowell -- the example is not minimal in that sense. The problem persists even without Ligatures=TeX. It also persists when I go from TNR (a TrueType font in an OpenType container) to, say, Minion Pro (a CFF font on an OpenType container). It disappears, though, when fontspec is removed altogether. – Nils L Mar 17 '13 at 13:49
I'm still not sure if this is something to take up with Adobe support since I have not had this problem with other pdf documents on which I used the export function. When people here say this is to local a problem, I partly agree. Only partly, because while I discovered the faultyness of LuaTeX pdfs when using Acrobat's Export feature, it may well cause problems in other contexts too. The question that remains, therefore, is whether this is the pdf produced by LuaLaTeX (in combination with fontspec) really faulty or is Acrobat's export feature faulty? – Christoph Mar 17 '13 at 18:21
I have voted to reopen, as it is a genuine problem, and there is some difference between xelatex and lualatex behaviour here. I don't know if it is related to tex.stackexchange.com/q/55098/15925. It would be nice to have an explanation. – Andrew Swann Mar 17 '13 at 18:27
@Christoph: As it is only Adobe support can tell us what Acrobat thinks is wrong with the PDF - or does Acrobat preflight produce any warnings helping here? – Martin Schröder Mar 18 '13 at 10:25