Take the 2-minute tour ×
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.

Using lualatex on latest TeXLive 2012 I am not able to select Libertine Mono by its full name via fontspec. luaotfload is finding the font and it is written into ~/.texlive2012/texmf-var/luatex-cache/generic/names/otfl-names.lua

However I am able to select the different styles by their psname like LinLibertineMO. Is there something wrong with the font itself or am I doing something wrong?

edit: As requestet a working example.

\documentclass{scrartcl}
\usepackage[english]{babel}
\usepackage{fontspec}
\usepackage{blindtext}
\setmainfont{Linux Libertine O}
\setsansfont{Linux Biolinum O}
% \setmonofont{Linux Libertine Mono O}

\begin{document}

\blindtext

\end{document}

Uncommenting setmonofont leads to not working:

! fontspec error: "font-not-found"
! 
! The font "LinuxLibertineMonoO" cannot be found.
!  
! See the fontspec documentation for further information.

Here’s an excerpt from ~/.texlive2012/texmf-var/luatex-cache/generic/names/otfl-names.lua

{
["familyname"]="Linux Libertine Mono O",
["filename"]={ "LinLibertine_M.otf", false },
["fontname"]="LinLibertineMO",
["fullname"]="Linux Libertine Mono O",
["names"]={
 ["family"]="Linux Libertine Mono O",
 ["fullname"]="Linux Libertine Mono O",
 ["psname"]="LinLibertineMO",
 ["subfamily"]="Mono",
},
share|improve this question

closed as off-topic by Xavier, dustin, Werner, egreg, Andrew Swann Jul 26 '13 at 19:18

  • 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.

    
Can you apply this patch: gist.github.com/phi-gamma/5457042 to otfl-font-nms.lua and test again? It would appear that Libertine Mono has a quirk wrt to subfamily designation. –  phg Apr 25 '13 at 2:24
1  
Ok, I have updated the gist with a test for the font name; it should now match the non-bold variants unless requested otherwise. Thanks for testing. Fwiw, with problems like this, run otfinfo -i on the font file to list possible identifiers. The safe bet is almost always on what the field Postscript name says (“LinLibertineMO” in this case). –  phg Apr 25 '13 at 8:44
1  
Yep, now it works. Could you submit your patch upstream? The problem with the postcript name is, that one can only select a specific style (regular, italic, bold, etc.). –  Tobias Schula Apr 25 '13 at 11:52
1  
It’s on its way. Hopefully it will make it into the next bugfix release. You’re right, of course, that the automation fontspec does is probably not possible when working with psname/filename based loading. –  phg Apr 25 '13 at 12:48
4  
This question was related to a bug in Libertine Mono, which has been corrected. –  Xavier Jul 26 '13 at 18:37
show 1 more comment