3

I'm trying to use the Roboto font in a beamer presentation, built with pdftex. I installed the roboto package, but when trying to build, I get the following error:

Trying to make PK font Roboto-Light-lf-t1--base at 657 DPI...
Running miktex-makemf.exe...
miktex-makemf: The Roboto-Light-lf-t1--base source file could not be found.

Running ttf2pk.exe...
miktex-makepk: PK font Roboto-Light-lf-t1--base could not be created.
)
!pdfTeX error: pdflatex.EXE (file Roboto-Light-lf-t1--base): Font Roboto-Light- lf-t1--base at 657 not found

I tried running updmap.exe in a console, both as user and admin, but it didn't resolve the problem. An MWE is included below.

\documentclass{beamer}

\usepackage[T1]{fontenc}
\usepackage[sfdefault,light]{roboto}

\title{Title}
\author{Me}

\begin{document}

\maketitle

\begin{frame}
 \frametitle{First slide}
 \begin{itemize}
  \item Item
  \item Item
 \end{itemize}
\end{frame}

\end{document}

Update: I just tried updating my packages and saw that the roboto package is obsolete. Could this have something to do with the error? Does this mean I can't use the font?

Mangara
  • 287
  • Which tex system do you use? – Ulrike Fischer May 22 '15 at 19:19
  • @UlrikeFischer MiKTeX 2.9 with the TeXworks editor. – Mangara May 22 '15 at 19:33
  • I can use the font without problems (and my system is up-to-date). Perhaps the package has been renamed. Synchronize in the package manager (user and admin) in the repository menu your package database and run updates. Run also updmap. – Ulrike Fischer May 22 '15 at 21:54
  • Run from the command line ‘updmap’, to refresh the type1 files database. – Bernard May 22 '15 at 23:32
  • Ever find a solution @Mangara ? – Stormie Feb 08 '16 at 19:39
  • 1
    @Stormie Not with pdftex. I ended up switching to XeTeX, which was quite painless and made this very easy (it can use system fonts). – Mangara Feb 09 '16 at 20:21
  • A similar error happens to me with pdfLaTeX. I installed the package a few minutes ago, refreshed the file name database, and updated all the format files, but pdfLaTeX still gives these errors. – JRN Feb 21 '16 at 02:00
  • Possibly related: http://tex.stackexchange.com/q/154998/64175 – JRN Feb 21 '16 at 02:04
  • Works fine with TeXLive 2016 – samcarter_is_at_topanswers.xyz Dec 19 '16 at 17:05
  • 4
    I'm voting to close this question as off-topic because solved by switching to xelatex – samcarter_is_at_topanswers.xyz Dec 19 '16 at 17:05
  • @samcarter I don't see how not finding a solution makes the question off-topic. Does this site have a policy of closing old unanswered questions? – Mangara Dec 20 '16 at 18:45
  • @Mangara Please ignore the words "off-topic", most of the closed questions carry these words because it is the one reason where one can enter a custom close reason. As for the closure itself, from reading the comments I had the impression that the problem was solved, if you are still looking for an answer, feel free to vote for reopen. But before reopening, maybe report if Bernhard's suggestion worked. – samcarter_is_at_topanswers.xyz Dec 21 '16 at 13:30
  • @samcarter Okay, that makes sense. It's true that I'm not looking for a solution any more, as xelatex didn't have this issue. I'm pretty sure (but not 100%) that I tried Bernard's suggestion and it didn't help. – Mangara Dec 22 '16 at 17:43

0 Answers0