[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#666681: marked as done (dvips (and dvipdfm) choke on (some ?) user fonts)

Your message dated Sun, 1 Apr 2012 20:47:11 +0200
with message-id <CAEnRq5OgAkH6bqL7WWWX1chYKJd_hq5EbVV0xTj2hinHDUfJUg@mail.gmail.com>
and subject line Re: Bug#666681: dvips (and dvipdfm) choke on (some ?) user fonts
has caused the Debian Bug report #666681,
regarding dvips (and dvipdfm) choke on (some ?) user fonts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
666681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666681
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: texlive-binaries
Version: 2011.20120328-1
Severity: important

  Hello,

  Upon upgrading to texlive 2011, my user-installed fonts, in
~/texmf/fonts simply aren't recognized anymore by dvips and/or dvipdfm:

~ dvips main                  
This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com)
' TeX output 2012.03.31:2240' -> main.ps

kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+264/600 --dpi 864 cahr8r
mktexpk: don't know how to create bitmap font for cahr8r.
mktexpk: perhaps cahr8r is missing from the map file.
kpathsea: Appending font creation commands to missfont.log.
dvips: Font cahr8r not found; using cmr10
</usr/share/texlive/texmf-dist/fonts/pk/ljfour/public/cm/dpi600/cmr10.pk>
kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 2+293/600 --dpi 1493 cahr8r
mktexpk: don't know how to create bitmap font for cahr8r.
mktexpk: perhaps cahr8r is missing from the map file.

dvips: Font cahr8r not found; using cmr10
</usr/share/texlive/texmf-dist/fonts/pk/ljfour/public/cm/dpi600/cmr10.pk>
kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+437/600 --dpi 1037 cahr8r
mktexpk: don't know how to create bitmap font for cahr8r.
mktexpk: perhaps cahr8r is missing from the map file.

dvips: Font cahr8r not found; using cmr10
</usr/share/texlive/texmf-dist/fonts/pk/ljfour/public/cm/dpi600/cmr10.pk>
dvips: ! invalid char 224 from font cahr8r

  Interestingly, the error message comes from parsing the file
/usr/share/texlive/texmf-dist/fonts/pk/ljfour/public/cm/dpi600/cmr10.pk.

  I never had problems with this setup, although I've used that on
Debian unstable ever since 2007. The font is a plain postscript
font. Files related to it are 

~/texmf find | grep cah   
./fonts/map/dvips/updmap/cah.map
./fonts/afm/madtype/casinohand/cahr8a.afm
./fonts/type1/madtype/casinohand/cahr8a.pfb
./fonts/vf/madtype/casinohand/cahr7t.vf
./fonts/vf/madtype/casinohand/cahro8c.vf
./fonts/vf/madtype/casinohand/cahrc8t.vf
./fonts/vf/madtype/casinohand/cahrc7t.vf
./fonts/vf/madtype/casinohand/cahr8c.vf
./fonts/vf/madtype/casinohand/cahro8t.vf
./fonts/vf/madtype/casinohand/cahr8t.vf
./fonts/vf/madtype/casinohand/cahro7t.vf
./fonts/tfm/madtype/casinohand/cahro8t.tfm
./fonts/tfm/madtype/casinohand/cahrc7t.tfm
./fonts/tfm/madtype/casinohand/cahr8t.tfm
./fonts/tfm/madtype/casinohand/cahr8c.tfm
./fonts/tfm/madtype/casinohand/cahro7t.tfm
./fonts/tfm/madtype/casinohand/cahro8c.tfm
./fonts/tfm/madtype/casinohand/cahr8a.tfm
./fonts/tfm/madtype/casinohand/cahrc8t.tfm
./fonts/tfm/madtype/casinohand/cahro8r.tfm
./fonts/tfm/madtype/casinohand/cahr8r.tfm
./fonts/tfm/madtype/casinohand/cahr7t.tfm
./tex/latex/psfonts/ts1cah.fd
./tex/latex/psfonts/8rcah.fd
./tex/latex/psfonts/t1cah.fd
./tex/latex/psfonts/ot1cah.fd

  It was enabled using

~ updmap --enable Map cah.map

  (ages ago, but doing that again doesn't improve the situation).

  xdvi shows the font correctly, and latex has no problems compiling.

  Any help greatly appreciated, as for now it simply prevents me from
going on with some of my work...

  In case that is useful:

 ~ env | grep TEX
TEXINPUTS=/home/vincent/Recherche/utils/tex:/home/vincent/Textes/tex:


  Cheers,

        Vincent


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages texlive-binaries depends on:
ii  dpkg            1.16.2
ii  ed              1.6-1
ii  install-info    4.13a.dfsg.1-9
ii  libc6           2.13-27
ii  libfontconfig1  2.8.0-3.1
ii  libfreetype6    2.4.9-1
ii  libgcc1         1:4.7.0-1
ii  libgraphite3    1:2.3.1-0.2
ii  libkpathsea6    2011.20120328-1
ii  libpng12-0      1.2.47-2
ii  libpoppler13    0.16.7-3
ii  libptexenc1     2011.20120328-1
ii  libstdc++6      4.7.0-1
ii  libt1-5         5.1.2-3.5
ii  libx11-6        2:1.4.4-4
ii  libxaw7         2:1.0.9-3
ii  libxmu6         2:1.1.0-3
ii  libxpm4         1:3.5.9-4
ii  libxt6          1:1.1.1-2
ii  perl            5.14.2-9
ii  tex-common      3.5
ii  texlive-common  2011.20120322-1
ii  zlib1g          1:1.2.6.dfsg-2

Versions of packages texlive-binaries recommends:
ii  luatex          0.70.1-3
ii  python          2.7.2-10
ii  ruby            4.8
ii  ruby1.8 [ruby]  1.8.7.352-2
ii  texlive-base    2011.20120322-1
ii  tk8.4 [wish]    8.4.19-4
ii  tk8.5 [wish]    8.5.11-1

texlive-binaries suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
  Hello,

On Sun, Apr 1, 2012 at 4:02 AM, Norbert Preining <preining@logic.at> wrote:
> On Sa, 31 Mär 2012, Vincent Fourmond wrote:
>> ~ updmap --enable Map cah.map
>
> Ahhhh, you are running *user* controlled map files ... that is dangerous,
> and there is no way that this can work forever without your intervention.
>
> So, can you show me a run of
>        updmap
> and then at the end it will tell you something about a log file
> genereated, please send this, too (zipped).

  Hmm, it seems that running updmap alone has fixed the problem. (it
wasn't enough before, though) I'm puzzled, as I'm almost sure I had
tried this yesterday.

  Sorry to have wasted your time then.

  Thanks !

      Vincent, back to work

--- End Message ---
Reply to: