The standard Adobe fonts on Unix appear to have more accurate POINT_SIZE fields than PIXEL_SIZE fields. The pixel size can be derived from POINT_SIZE and RESOLUTION_Y, so we should compute it that way.

reassign to bstell and mark it as ---

--> ftang

bulk move NEW FUTURE bug to ASSIGN

What's up with this bug? If we never plan to fix it, just say so... Is this even relevant with the new xft/freetype/whatever stuff that's going on?

This appears to only relate to the core X fonts. Unless some has feeling about this bug, I recommend we close it.

This bug came from a newsgroup discussion Erik and I had ages ago. The problem is that the standard X bitmap fonts are all specified in points. The pixel sizes defined in the fonts are derived from the point values but there are roundoff errors so selecting these fonts by their pixel values is not monotonic. Since X thinks in terms of points, the idea is that mozilla does so as well when talking to the X server. This doesn't apply to scaleable fonts because the pixel <-> point mapping occurs ar run-time.

what a hack. I have not touch mozilla code for 2 years. I didn't read these bugs for 2 years. And they are still there. Just close them as won't fix to clean up.

Mass Re-open of Frank Tangs Won't fix debacle. Spam is his responsibility not my own

Mass Re-assinging Frank Tangs old bugs that he closed won't fix and had to be re-open. Spam is his fault not my own