usepackage[T1]{fontenc} doesn't use cm-super or cm-super unicode despite being installed
up vote
0
down vote
favorite
Some Bitmap font is being used instead.
Minimal working example:
documentclass{article}
usepackage[T1]{fontenc}
usepackage{lipsum}
begin{document}
lipsum
end{document}
Expected output:
Pretty text that isn't cancer.
What I get:
Cancer. See logfile.
Logfile:
Clicky
My updmap.cfg
fonts font-encodings
asked Dec 5 at 14:16
Rick Rickson
313
|
show 6 more comments
up vote
0
down vote
favorite
Some Bitmap font is being used instead.
Minimal working example:
documentclass{article}
usepackage[T1]{fontenc}
usepackage{lipsum}
begin{document}
lipsum
end{document}
Expected output:
Pretty text that isn't cancer.
What I get:
Cancer. See logfile.
Logfile:
Clicky
My updmap.cfg
fonts font-encodings
asked Dec 5 at 14:16
Rick Rickson
313
@Sveinung that is not true, in TeXLive cm-super is normally the default.
– daleif
Dec 5 at 14:27
1
What exactly have you installed? Is this a repackaged TeXLive for slackware? Did you install all of it or just parts of it?
– daleif
Dec 5 at 14:27
What doeskpsewhich sfrm1000.pfbreport? When I compile your MWE using my installation of upstream TeXLive then this font file is being listed as being included. Your installation is a bit strange, as I have a much newer lipsum installed
– daleif
Dec 5 at 14:30
kpsewhich sfrm1000.pfb: /usr/share/texmf-dist/fonts/type1/public/cm-super/sfrm1000.pfb Also, yeah ,it's a Slackware thing, from slackbuilds.org, but the base package has made it into the current snapshot. The "extras" package is a huge one with all sorts of, well, extra packages. I installed everything.
– Rick Rickson
Dec 5 at 14:35
how aboutkpsewhich cm-super-t1.enc, otherwise try installing upstream TL instead (tug.org/texlive). I usually recommend to not installing it as root, but rather install it as yourself in a folder you own in say/opt, and then adding this path to the $PATH variable.
– daleif
Dec 5 at 14:45
|
show 6 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Some Bitmap font is being used instead.
Minimal working example:
documentclass{article}
usepackage[T1]{fontenc}
usepackage{lipsum}
begin{document}
lipsum
end{document}
Expected output:
Pretty text that isn't cancer.
What I get:
Cancer. See logfile.
Logfile:
Clicky
My updmap.cfg
fonts font-encodings
asked Dec 5 at 14:16
Rick Rickson
313
Some Bitmap font is being used instead.
Minimal working example:
documentclass{article}
usepackage[T1]{fontenc}
usepackage{lipsum}
begin{document}
lipsum
end{document}
Expected output:
Pretty text that isn't cancer.
What I get:
Cancer. See logfile.
Logfile:
Clicky
My updmap.cfg
fonts font-encodings
fonts font-encodings
asked Dec 5 at 14:16
Rick Rickson
313
asked Dec 5 at 14:16
Rick Rickson
313
edited Dec 5 at 15:47
asked Dec 5 at 14:16
Rick Rickson
313
asked Dec 5 at 14:16
Rick Rickson
313
asked Dec 5 at 14:16
Rick Rickson
313
313
@Sveinung that is not true, in TeXLive cm-super is normally the default.
– daleif
Dec 5 at 14:27
1
What exactly have you installed? Is this a repackaged TeXLive for slackware? Did you install all of it or just parts of it?
– daleif
Dec 5 at 14:27
What doeskpsewhich sfrm1000.pfbreport? When I compile your MWE using my installation of upstream TeXLive then this font file is being listed as being included. Your installation is a bit strange, as I have a much newer lipsum installed
– daleif
Dec 5 at 14:30
kpsewhich sfrm1000.pfb: /usr/share/texmf-dist/fonts/type1/public/cm-super/sfrm1000.pfb Also, yeah ,it's a Slackware thing, from slackbuilds.org, but the base package has made it into the current snapshot. The "extras" package is a huge one with all sorts of, well, extra packages. I installed everything.
– Rick Rickson
Dec 5 at 14:35
how aboutkpsewhich cm-super-t1.enc, otherwise try installing upstream TL instead (tug.org/texlive). I usually recommend to not installing it as root, but rather install it as yourself in a folder you own in say/opt, and then adding this path to the $PATH variable.
– daleif
Dec 5 at 14:45
|
show 6 more comments
@Sveinung that is not true, in TeXLive cm-super is normally the default.
– daleif
Dec 5 at 14:27
1
What exactly have you installed? Is this a repackaged TeXLive for slackware? Did you install all of it or just parts of it?
– daleif
Dec 5 at 14:27
What doeskpsewhich sfrm1000.pfbreport? When I compile your MWE using my installation of upstream TeXLive then this font file is being listed as being included. Your installation is a bit strange, as I have a much newer lipsum installed
– daleif
Dec 5 at 14:30
kpsewhich sfrm1000.pfb: /usr/share/texmf-dist/fonts/type1/public/cm-super/sfrm1000.pfb Also, yeah ,it's a Slackware thing, from slackbuilds.org, but the base package has made it into the current snapshot. The "extras" package is a huge one with all sorts of, well, extra packages. I installed everything.
– Rick Rickson
Dec 5 at 14:35
how aboutkpsewhich cm-super-t1.enc, otherwise try installing upstream TL instead (tug.org/texlive). I usually recommend to not installing it as root, but rather install it as yourself in a folder you own in say/opt, and then adding this path to the $PATH variable.
– daleif
Dec 5 at 14:45
@Sveinung that is not true, in TeXLive cm-super is normally the default.
– daleif
Dec 5 at 14:27
@Sveinung that is not true, in TeXLive cm-super is normally the default.
– daleif
Dec 5 at 14:27
1
1
What exactly have you installed? Is this a repackaged TeXLive for slackware? Did you install all of it or just parts of it?
– daleif
Dec 5 at 14:27
What exactly have you installed? Is this a repackaged TeXLive for slackware? Did you install all of it or just parts of it?
– daleif
Dec 5 at 14:27
What does
kpsewhich sfrm1000.pfb report? When I compile your MWE using my installation of upstream TeXLive then this font file is being listed as being included. Your installation is a bit strange, as I have a much newer lipsum installed– daleif
Dec 5 at 14:30
What does
kpsewhich sfrm1000.pfb report? When I compile your MWE using my installation of upstream TeXLive then this font file is being listed as being included. Your installation is a bit strange, as I have a much newer lipsum installed– daleif
Dec 5 at 14:30
kpsewhich sfrm1000.pfb: /usr/share/texmf-dist/fonts/type1/public/cm-super/sfrm1000.pfb Also, yeah ,it's a Slackware thing, from slackbuilds.org, but the base package has made it into the current snapshot. The "extras" package is a huge one with all sorts of, well, extra packages. I installed everything.
– Rick Rickson
Dec 5 at 14:35
kpsewhich sfrm1000.pfb: /usr/share/texmf-dist/fonts/type1/public/cm-super/sfrm1000.pfb Also, yeah ,it's a Slackware thing, from slackbuilds.org, but the base package has made it into the current snapshot. The "extras" package is a huge one with all sorts of, well, extra packages. I installed everything.
– Rick Rickson
Dec 5 at 14:35
how about
kpsewhich cm-super-t1.enc, otherwise try installing upstream TL instead (tug.org/texlive). I usually recommend to not installing it as root, but rather install it as yourself in a folder you own in say /opt, and then adding this path to the $PATH variable.– daleif
Dec 5 at 14:45
how about
kpsewhich cm-super-t1.enc, otherwise try installing upstream TL instead (tug.org/texlive). I usually recommend to not installing it as root, but rather install it as yourself in a folder you own in say /opt, and then adding this path to the $PATH variable.– daleif
Dec 5 at 14:45
|
show 6 more comments
1 Answer
1
active
oldest
votes
up vote
3
down vote
Turned out the package of my distribution (Slackware 14.2-current) was faulty.
Getting rid of it and going full TL upstream fixed the issue.
answered Dec 5 at 15:46
Rick Rickson
313
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Turned out the package of my distribution (Slackware 14.2-current) was faulty.
Getting rid of it and going full TL upstream fixed the issue.
answered Dec 5 at 15:46
Rick Rickson
313
add a comment |
up vote
3
down vote
Turned out the package of my distribution (Slackware 14.2-current) was faulty.
Getting rid of it and going full TL upstream fixed the issue.
answered Dec 5 at 15:46
Rick Rickson
313
add a comment |
up vote
3
down vote
up vote
3
down vote
Turned out the package of my distribution (Slackware 14.2-current) was faulty.
Getting rid of it and going full TL upstream fixed the issue.
answered Dec 5 at 15:46
Rick Rickson
313
Turned out the package of my distribution (Slackware 14.2-current) was faulty.
Getting rid of it and going full TL upstream fixed the issue.
answered Dec 5 at 15:46
Rick Rickson
313
answered Dec 5 at 15:46
Rick Rickson
313
answered Dec 5 at 15:46
Rick Rickson
313
answered Dec 5 at 15:46
Rick Rickson
313
313
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f463328%2fusepackaget1fontenc-doesnt-use-cm-super-or-cm-super-unicode-despite-being%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
@Sveinung that is not true, in TeXLive cm-super is normally the default.
– daleif
Dec 5 at 14:27
1
What exactly have you installed? Is this a repackaged TeXLive for slackware? Did you install all of it or just parts of it?
– daleif
Dec 5 at 14:27
What does
kpsewhich sfrm1000.pfbreport? When I compile your MWE using my installation of upstream TeXLive then this font file is being listed as being included. Your installation is a bit strange, as I have a much newer lipsum installed– daleif
Dec 5 at 14:30
kpsewhich sfrm1000.pfb: /usr/share/texmf-dist/fonts/type1/public/cm-super/sfrm1000.pfb Also, yeah ,it's a Slackware thing, from slackbuilds.org, but the base package has made it into the current snapshot. The "extras" package is a huge one with all sorts of, well, extra packages. I installed everything.
– Rick Rickson
Dec 5 at 14:35
how about
kpsewhich cm-super-t1.enc, otherwise try installing upstream TL instead (tug.org/texlive). I usually recommend to not installing it as root, but rather install it as yourself in a folder you own in say/opt, and then adding this path to the $PATH variable.– daleif
Dec 5 at 14:45