Red Hat Bugzilla – Bug 864711
texlive generates unneeded/unwanted bitmap fonts
Last modified: 2015-03-04 20:21:13 EST
Description of problem:
texlive-2012 installs cm-super fonts by default so one would hope that they will be used in a preference to bitmap fonts. Actually this is the case, to an extent, only if I am running a cyrillic sample then I see:
kpathsea: Running mktextfm labx1440
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input labx1440
and in a short order and trivial samples I end up in
~/.texlive2012/texmf-var/fonts/ with an extra 372K in the following files:
plus an extra time it takes to generate that. Curiously enough I eventually
see in log:
Output written on sample.pdf (1 page, 37175 bytes).
and 'pdffonts sample.pdf' show:
uni object ID
------------------------------------ ----------------- ---------------- --- --- --- ---------
TSAQGP+SFBX1728 Type 1 Custom yes yes no 14 0
HNTONM+SFRM1200 Type 1 Custom yes yes no 15 0
GDVKRN+SFBX1440 Type 1 Custom yes yes no 16 0
so all that hullabaloo was for naught but why it happened in the first place?
always with bimaps not yet generated
That does not seem to be new. I see that same on texlive-2007 installation with additionally installed cm-super fonts; I simply did not notice that right away as bitmaps were done before I added cm-super.
Created attachment 624337 [details]
sample .tex file which is causing a generation of spurious bitmaps
I suspect is just a per-user font cache which speeds up the next compilation. Not really sure it is a bug. Better to say a feature.
(In reply to comment #2)
> I suspect is just a per-user font cache which speeds up the next
> compilation. Not really sure it is a bug. Better to say a feature.
Generating bitmap files which will be not used for anythig save a prevention of doing that again does not strike me as overly useful; especially that they are stored in home directories so with a multiple users on one machine an amount of junk will multiply. Maybe one can pass that for an annoyance without an obvious resolution, although I did not recall that nastinies with other Type 1 fonts, but calling that "a feature" looks to me like a big stretch.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.