Font problems in texlive 2019

**velenik** · 24-Jul-2019, 01:37

Since updating to texlive 2019 (last week or so), many tex files are not compiling anymore, due to some font problems. Below are a minimal latex file that shows up the error, and the actual error message on compilation.

Note: all these files were compiling properly on texlive 2018 (that is, before the recent update).

%%%%%%%%%

\documentclass{article}

\usepackage[condensed]{roboto}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}

\begin{document}

\textsf{Aa}

\end{document}

%%%%%%%%%

When compiling this file (with pdflatex), I get the following error message:

[...]
LaTeX Font Warning: Font shape `T1/cmr/regular/n' undefined
(Font) using `T1/cmr/m/n' instead on input line 7.

(/usr/share/texmf/tex/latex/roboto/T1RobotoCondensed-LF.fd) [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./test.aux)

LaTeX Font Warning: Some font shapes were not available, defaults substituted.

){/usr/share/texmf/fonts/enc/dvips/cm-super/cm-super-t1.enc}
!pdfTeX error: pdflatex (file rbto_idpkzy.enc): cannot open encoding file for reading
==> Fatal error occurred, no output PDF file produced!

The file rbto_idpkzy.enc indeed does not exist in my tree (but many other rbto_xxxxxx.enc files do).
I have the same problem replacing roboto by many other sans serif fonts.

**john_hudson** · 24-Jul-2019, 13:35

Just a guess but as LaTeX now uses utf-8 as the default encoding and your error message refers to

cm-super-t1.enc

, is there an encoding conflict?

**velenik** · 25-Jul-2019, 00:20

Originally Posted by john_hudson

Just a guess but as LaTeX now uses utf-8 as the default encoding and your error message refers to , is there an encoding conflict?

Thanks for the suggestion. How should I test that?

Note that the exact same files were compiling without any problems 2 weeks ago before the transition from TeXLive 2018 to TeXLive2019 (and still compile fine on my office computer, as I locked all TeXLive packages there once I saw what happened at home; all other updates were made on this computer as well, so the problem undoubtly is due to the update of texlive-* packages). Also, only sans serif fonts seem to be an issue (and even that with some reservation: they seem to work fine in math mode).

**john_hudson** · 25-Jul-2019, 13:50

Sorry I am not sure but I wonder if, as a result of https://www.latex-project.org/news/l...s/ltnews28.pdf, people have ‘tidied up’ some packages in ways which mean that, though the intention was to support legacy encodings, these are no longer supported correctly.

**velenik** · 26-Jul-2019, 09:00

Yes, maybe you're right, but I really hope, however, that it's simply a bug in the packaging of TeXLive 2019 for tumbleweed and that it will be repaired at some point in the not too distant future. Would you happen to know whether there is a simple way to downgrade TexLive back to the 2018 version in tumbleweed? It's really a problem for me, as I am using latex almost everyday... If there is no simple way, I might just install a version of the TeXLive 2019 tree manually from tug.org and see whether that works.

In any case, thanks for your comments!