[OS X TeX] Screwed up fonts

Peter Dyballa Peter_Dyballa at Web.DE
Mon Jun 20 16:50:08 CEST 2005

Am 20.06.2005 um 15:13 schrieb Michael Kubovy:

> [1{/usr/local/
> teTeX/share/texmf.local/fonts/map/pdftex/context/pdftex.map}

The map file is found and is being used! So the problem might be that  
the right entries are not contained yet in the MAP file ...

When I launch updmap it starts with these lines:

	updmap: This is updmap, version 1107552857
	updmap: using transcript file  
	updmap: initial config file is  
	updmap: configuration file updated:  

your's has no such 'initial config file':

	updmap: This is updmap, version 1107552857
	updmap: using transcript file  

For me many of those files that got the header 'Scanning for MixedMap  
entries' are under  'updmap: Scanning for LW35 support files' ...

What is in Terminal

	ls -l /usr/local/teTeX/share/texmf.tetex/web2c/updmap.cfg  

showing? If you only see two files listed, could you try to copy the  
system's configuration file to become the local one too and run updmap  
again? It goes in Terminal

	sudo cp /usr/local/teTeX/share/texmf.tetex/web2c/updmap.cfg  
	sudo updmap --nohash

What is contained in  
/usr/local/teTeX/share/texmf.local/web2c/updmap.log? In Terminal a 'cat  
/usr/local/teTeX/share/texmf.local/web2c/updmap.log' would show it. Is  
it more than three lines?

I get the feeling that you made a mistake when configuring the TeX  
i-Package ... that you missed to check LW35 or LaserWriter 35 support,  
i.e. the support for the usual 35 built-in PostScript fonts. Did you  
check or un-check any MAP files? When did you do the last update? When  
could you produce PDF files with smooth fonts in them?

Could be this time consuming step makes it alright again:

	sudo updmap --nohash --disable bsr ; sudo updmap --nohash --enable  
	sudo updmap --nohash --disable bsr-interpolated ; sudo updmap --nohash  
--enable Map=bsr-interpolated
	sudo updmap --nohash --disable cbgreek ; sudo updmap --nohash --enable  
	sudo updmap --nohash --disable ccpl ; sudo updmap --nohash --enable  
	sudo updmap --nohash --disable cm-super-t1 ; sudo updmap --nohash  
--enable Map=cm-super-t1
	sudo updmap --nohash --disable cm-super-ts1 ; sudo updmap --nohash  
--enable Map=cm-super-ts1
	sudo updmap --nohash --disable cm-super-t2 ; sudo updmap --nohash  
--enable Map=cm-super-t2
	sudo updmap --nohash --disable cm-super-t2a ; sudo updmap --nohash  
--enable Map=cm-super-t2a
	sudo updmap --nohash --disable cm-super-t2b ; sudo updmap --nohash  
--enable Map=cm-super-t2b
	sudo updmap --nohash --disable cm-super-t2c ; sudo updmap --nohash  
--enable Map=cm-super-t2c
	sudo updmap --nohash --disable cm-super-x2 ; sudo updmap --nohash  
--enable Map=cm-super-x2
	sudo updmap --nohash --disable cs ; sudo updmap --nohash --enable  
	sudo updmap --nohash --disable pl ; sudo updmap --nohash --enable  
	sudo updmap --nohash --disable vnr ; sudo updmap --nohash --enable  
	sudo updmap --nohash --disable ttcmex ; sudo updmap --nohash --enable  
	sudo updmap --nohash --disable eurosym ; sudo updmap --nohash --enable  
	sudo updmap --nohash --disable hoekwater ; sudo updmap --nohash  
--enable Map=hoekwater

updmap does not need texhash, usually it invokes it, except you tell it  
'--nohash' because usually no new files are being created, only old  
ones being updated.

The more I ponder over your case the more I get confused myself ...  
it's not likely to happen! Yes: the first lines of your TeX file,  
before ``\begin{document}´´ could make things become more understood.  
And a copy of  
pdftex_dl14.map (the actual file pdftex.map points to) please too!

I'm going to have a break soon, approximately one hour, then, at home,  
I'll return to your case!



Never be led astray onto the path of virtue.

--------------------- Info ---------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
           & FAQ: http://latex.yauh.de/faq/
TeX FAQ: http://www.tex.ac.uk/faq
List Post: <mailto:MacOSX-TeX at email.esm.psu.edu>

More information about the macostex-archives mailing list