On Tue, 30 Jan 2007 00:52:05 -0700, Taco Hoekwater wrote:

Idris Samawi Hamid wrote:

...

Dear gang,

Does anyone understand the following font error? The file used to work for over a year till I installed the latest ConTeXt files:

It seems there is a problem with the map file for your MinionPro font: pdftex clearly believes it is a metafont bitmap instead of a scalable font, and that only happens if it does not have the proper font map information.

I see, any ideas on what I should do? I was actually thinking about just starting over again from scratch, reinstalling ConTeXt, and reinstalling all my auxilliary fonts etc. from scratch but that's a lot of work... Best Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Hi Taco, On Tue, 30 Jan 2007 08:02:59 -0700, Taco Hoekwater wrote:

...

...

...

Does anyone understand the following font error? The file used to work for over a year till I installed the latest ConTeXt files: It seems there is a problem with the map file for your MinionPro font: pdftex clearly believes it is a metafont bitmap instead of a scalable font, and that only happens if it does not have the proper font map information.

I see, any ideas on what I should do?

First, find it. Then make sure you have a \loadmapfile statement with the right filename. Then verify that kpsewhich can find the map file by running 'kpsewhich <filename>'. After all that, check that ConTeXt actually reads a map file, by that name, and that it is the right one (by checking the screen output).

Somewhere along this chain of events, it should start working, or an error should become obvious.

There must be an error or some new feature in recent releases of ConTeXt that's causing this. I backed up to ConTeXt2006-12-07, only a month ago, and everything works fine. I checked; typescripts are loading mapfiles eg \loadmapfile[texnansi-axow-adobe-minion.map] and the mapfiles are indeed there eg \ConTeXt\tex\texmf-fonts\fonts\map\pdftex\context As for tfm's, eg texnansi-axow-MinionPro-Regular.tfm is in \ConTeXt\tex\texmf-fonts\fonts\tfm\adobe\minion Has the ConTeXt TDS changed? This must be a new ConTeXt bug/feature; I don't know which. Oh Please, please, please don't make me rebuild this complicated font setup from scratch! :-) Best Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Idris Samawi Hamid wrote:

On Tue, 30 Jan 2007 00:52:05 -0700, Taco Hoekwater wrote:

...

Idris Samawi Hamid wrote:

...

Dear gang,

Does anyone understand the following font error? The file used to work for over a year till I installed the latest ConTeXt files:

It seems there is a problem with the map file for your MinionPro font: pdftex clearly believes it is a metafont bitmap instead of a scalable font, and that only happens if it does not have the proper font map information.

I see, any ideas on what I should do?

I was actually thinking about just starting over again from scratch, reinstalling ConTeXt, and reinstalling all my auxilliary fonts etc. from scratch but that's a lot of work...

well, since you have luatex running ... in a while you can kick out tfm and map files since context mkiv can use the afm files and do map lines on the fly Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------