# LuaTeX: tex-text at 10 pt not loadable [closed]

I am trying to use LuaTeX with Linux Biolinum. It works fine with XeLaTeX, but when I'm running LuaLaTex, it gives me the following error:

This error is found in the fontenc.sty on line 100. I am using Texlive 2011 on Ubuntu 10.04, this is my example:

\documentclass[a5paper,ngerman]{article}
\usepackage[lutf8x]{luainputenc}
\usepackage{fontspec}
\setmainfont{Linux Biolinum}
\begin{document}
Text
\end{document}

-
Welcome to TeX.sx! Usually, we don't put a greeting or a "thank you" in our posts. While this might seem strange at first, it is not a sign of lack of politeness, but rather part of our trying to keep everything very concise. Upvoting is the preferred way here to say "thank you" to users who helped you. –  Roelof Spijker Nov 7 '11 at 15:39
AFAIK Biolinum is the default sf with package libertine. This package may be used with latex+dvips, pdflatex, xelatex and lualatex. –  Schweinebacke Nov 7 '11 at 15:46
The manual of luainputenc recommends to use the package only, if you are not using utf8 encoding for input and if you are using a 8 bit font. Biolinum is a unicode font. So you may - and maybe should - use utf8 input without loading luainputenc. –  Schweinebacke Nov 7 '11 at 15:50
What happens if you omit the luainputenc package? –  topskip Nov 7 '11 at 15:52
Based on @Greg's comment, I'd suggest this is 'too localized' - do others agree? –  Joseph Wright Nov 9 '11 at 14:00
show 6 more comments

## closed as too localized by Joseph Wright♦Nov 9 '11 at 17:42

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Your error message says ! Font \EU1/lmr/m/n/10=[lmroman10-regular]. EU1 is the encoding used by fontspec for xelatex. And the syntax with the [--]-braces around the font is xelatex syntax. So it looks as if fontspec for some reason is loading xelatex support files and then chokes over the wrong syntax. Which version of fontspec are you using? Did you check the log if perhaps an old version is used?

Addition: And I also advice against the use of luainputenc. It should be used only if really needed and then carefully.

-

The font is called Linux Biolinum O. This is what you can do:

\documentclass[a5paper,ngerman]{article}
\usepackage{fontspec}
\usepackage[lutf8x]{luainputenc}
\setmainfont{Linux Biolinum O}
\begin{document}
Text
\end{document}


Don't use luainputenc if you can avoid it. And load fontspec before this package, since it defines the EU2 encoding (a transparent unicode "encoding").

-
Unfortunately, the error remains the same (I've tried Oh and Zero). Is there a special Lua-version of fontenc, or something? –  Greg Nov 7 '11 at 15:45
AFAIK the font name depends on the OS. –  Schweinebacke Nov 7 '11 at 15:45
@Schweinebacke the fonts in the texlive tree should have the same name, AFAIK –  topskip Nov 7 '11 at 15:55
@Patrick: AFAIK at least at Windows XP the font names are "Linux Libertine" and "Linux Biolinum" without the "O" at least using MiKTeX. –  Schweinebacke Nov 7 '11 at 16:14
@Schweinebacke No, the above test file also runs on Windows XP (using TeXlive 2011). The difference is (as I've heard) that the "O" fonts are the OpenType fonts. –  topskip Nov 7 '11 at 16:34
show 1 more comment

I've tested:

\documentclass[a5paper]{article}
\usepackage{libertine}
\begin{document}\sffamily
Text ÄÖÜ
\end{document}


and

\documentclass[a5paper]{article}
\usepackage{libertine}
\renewcommand*{\familydefault}{\sfdefault}
\begin{document}
Text ÄÖÜ
\end{document}


and

\documentclass[a5paper]{article}
\usepackage{fontspec}
\setmainfont{Linux Libertine O}
\begin{document}
Text ÄÖÜ
\end{document}


All of them worked very well with new net installation of TeX Live 2011 and lualatex, if the test files are utf8 encoded. So maybe you should update or reinstall your TeX Live.

-