Comment 30 for bug 321932

Revision history for this message
pauljohn32 (pauljohn) wrote : Re: ghostscript stop rendering with font errors

I think the problem is not in the fonts themselves, but in the other changes that the installer triggers. Here's why.

After removing the msttcorefonts from my system last month, and making sure the hints file was gone from /etc/defoma/hints, then I was able to print pdf files from Adobe Acrobat reader.

I got brave and re-installed the msttcorefonts installer, and crash. Printing stops half way through with lots of documents.

Then I tested this. I copied the msttcorefonts to my home directory in ~/.fonts, then I purged the msttcorefonts package. That removed everything successfully.

Now I still have access to those fonts in programs like open office, but the adobe reader also works properly.

Can you tell me how programs ask for fonts from the font server, or how one can track that process? Or, what is the path for fonts (I've not understood this since the pre-xfs days :(). I expect the pdf file may ask for something and it gets the first thing in the font path that matches. So maybe the msttcorefonts are not being used at all when Adobe works properly?