68373 - [ps] Mozilla uses only built-in AFM metrics

Status: RESOLVED FIXED

(Core :: Printing: Output, defect)

Description

[Peter 'Nidd' Novodvorsky]

281              nsAFMObject::AFM_ReadFile(const nsFont &aFontName)
282              {
...
289 dcone    1.10 char* AFMFileName= aFontName.name.ToNewUTF8String(); // file
we will open

AFMFileName contains the name of the nsFont. This is usually "serif", but
sometimes "san-serif", or "fixed".

290
291                 if(nsnull == AFMFileName)
292                   return (success);
293
294                   if((0==strcmp(AFMFileName,"..")) ||
(0==strcmp(AFMFileName,"."))) {
295                     Recycle(AFMFileName);
296                     return (success);
297                   }
298
299                  // Open the file
300                 mAFMFile = fopen((const char *)AFMFileName,"r");

So, this function opens file "serif", "san-serif", or "fixed" file in current
directory and looks for AFM metrics there!!!! So this functions doesn't work.
The possible solution is to look for .afm file in user-specified directory.

Another promblem, is when I try to use Unicode PS font from
http://bibliofile.mc.duke.edu/gww/fonts/Unicode.html mozilla makes a core when
tries to read metrics.

Comment 1

[Keyser Sose]

Marking NEW. Seems to make sense to me.

Comment 2

[Kevin McCluskey (gone)]

Added crash keyword set target to mozilla0.9.1

Comment 3

[dcone (gone)]

I don't understand the problem.. this will read in what every afm file, you just 
have to put it into the directory..those are just the defaults.

Comment 4

[Peter 'Nidd' Novodvorsky]

In what directory. I need to put afm files into current dictionary
and name them serif, san-serif, etc.?
I think there should be centralized font repositary?

Comment 5

[Asa Dotzler [:asa]]

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)

Comment 6

[Peter 'Nidd' Novodvorsky]

This bug is almost 1,5 years old. it is still critical and there is no work done
to fix it. I seems that it is not critical for you. Maybe we should lower the
severity and hope that it will be fixed?

Comment 7

[Roland Mainz]

Peter 'Nidd' Novodvorsky wrote:
> This bug is almost 1,5 years old. it is still critical and there is no work 
> done to fix it.

The Xprint module (which is a complete, full replacement for the PostScript
module) has this functionality (see
http://mozilla.org/releases/mozilla1.0/#printing).

Comment 8

[kill this account]

Now that the PS module has Truetype to Postscript printing (bug 144663) can we 
close this?

Comment 9

[Pete Zha]

fixed by bug 144663 since we can use true type font to print.