3

It seems my TeX system on OSX Mavericks is no longer able to find my system fonts. My tex documents no longer compile, and when I do:

$ xetex opentype-info.tex 

I get:

This is XeTeX, Version 3.1415926-2.5-0.9999.3 (TeX Live 2013)
restricted \write18 enabled.
entering extended mode
(/usr/local/texlive/2013/texmf-dist/tex/xetex/xetexfontinfo/opentype-info.texkpathsea:make_tex: Invalid fontname `Latin Modern Roman/ICU', contains ' '

! Font \testfont="Latin Modern Roman/ICU" at 12.0pt not loadable: Metric (TFM) 
file or installed font not found.
l.26 \font\testfont="\myfontname/ICU" at 12pt

The fonts I'm trying to use ARE in my OSX system fonts. I think the problem is that LaTeX can't locate them.

In LaTex I have declarations like:

\setsansfont{ChunkFive}

and

\newfontfamily\mytitlefont[Color=signalflare]{ChunkFive}

This is resulting in errors.

Any suggestions?

  • 1
    Interesting. I can verify it. – Marco Daniel Nov 12 '13 at 8:51
  • 2
    If it's not in the system fonts, one has to specify the font by file name, like \def\myfontname{[lmroman12-regular]} – egreg Nov 12 '13 at 12:12
  • Actually, the fonts I'm trying to use ARE in my OSX system fonts. I think the problem is that LaTeX can't locate them. In LaTex I have declarations like: \\setsansfont{ChunkFive} and \\newfontfamily\\mytitlefont[Color=signalflare]{ChunkFive} This is resulting in errors. – incandescentman Nov 13 '13 at 3:07
  • This question might be related to you problem. – Pouya Nov 13 '13 at 9:44
  • Does this only happen with fonts that contain whitespace? – Crissov Jan 31 '14 at 13:03
2

I had the same problem today after migrating my old user account to my new MacBook Pro. I had to purchase a cable (thanks to the new Thunderbolt I/O port) to connect the two machines together and in the intervening time I installed a fresh Tex installation from the MacTex package and verified the distribution was working with the latest version of TexShop (version 3.26).

With cable in hand (and $30 missing from my wallet) I ran Apple's Migration Assistant to transfer my old user account to the new machine. In the process it looks like Migration assistant broke the symbolic link to the texlive-2013 distribution.

In my case it appears migration assistant actually traversed the /usr/texbin link on my old machine and created a directory /usr/texbin in its place. Whether or not Migration Assistant was responsible, the problem is simple to fix.

mv /usr/texbin /usr/texbin.old
ln -s /Library/TeX/Distributions/.DefaultTeX/Contents/Programs/texbin /usr/texbin 
  • Welcome to TeX.SX! You can have a look at our starter guide to familiarize yourself further with our format. A suggestion: Do us a favour and change your username to something more telling than "user1234". – Martin Schröder Feb 1 '14 at 16:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.