Closed Bug 68373 Opened 23 years ago Closed 21 years ago

[ps] Mozilla uses only built-in AFM metrics

Categories

(Core :: Printing: Output, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla1.0.1

People

(Reporter: nidd, Assigned: dcone)

References

Details

(Keywords: crash, helpwanted)

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.
Marking NEW. Seems to make sense to me.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Added crash keyword set target to mozilla0.9.1
Keywords: crash
Target Milestone: --- → mozilla0.9.1
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.
Status: NEW → ASSIGNED
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?
Keywords: helpwanted
Target Milestone: mozilla0.9.1 → mozilla0.9.3
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Target Milestone: mozilla0.9.4 → mozilla0.9.6
Target Milestone: mozilla0.9.6 → mozilla1.0
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)
Target Milestone: mozilla1.0 → mozilla1.0.1
Summary: Mozilla uses only built-in AFM metrics → [ps] Mozilla uses only built-in AFM metrics
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?
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).
Blocks: 157675
Now that the PS module has Truetype to Postscript printing (bug 144663) can we 
close this?

fixed by bug 144663 since we can use true type font to print.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.