Bug 690567 - Broken type cast for TrueType fonts on 64bit architectures
Summary: Broken type cast for TrueType fonts on 64bit architectures
Status: RESOLVED WONTFIX
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Font API (show other bugs)
Version: 8.64
Hardware: PC Linux
: P4 normal
Assignee: Ken Sharp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-24 06:25 UTC by Dr. Werner Fink
Modified: 2010-08-13 09:28 UTC (History)
0 users

See Also:
Customer:
Word Size: ---

Attachments
ghostscript-8.60-truetype.dif (511 bytes, patch)
2009-06-24 06:26 UTC, Dr. Werner Fink 		Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dr. Werner Fink 2009-06-24 06:25:27 UTC 
There is a small problem shown by new gcc with the types used
in the TrueType fonts handling.
Comment 1 Dr. Werner Fink 2009-06-24 06:26:06 UTC 
Created attachment 5152 [details]
ghostscript-8.60-truetype.dif

this small patch avoids the problem
Comment 2 Ray Johnston 2009-06-25 10:17:01 UTC 
This patch needs _careful_ review.
Comment 3 Ken Sharp 2009-06-26 00:09:37 UTC 
All PostScript & PDF patterns/shadings can be represented as patterns or
shadings in an output PDF file, so there is (generally at least) no need to fall
back to conversion into an image or images.

I haven't searched exhaustively, but I haven't seen a PS/PDF file exercise this
path.

The problem doesn't seem to be pdfwrite, the reference counting takes place in
the graphics library.
Comment 4 Ken Sharp 2009-06-26 00:11:40 UTC 
<sigh> Sorry, comment #3 was intended for a different issue....
Comment 5 Dr. Werner Fink 2009-06-26 02:10:38 UTC 
No problem ... I'm familiar with the handling of large numbers of
bugzilla entries ;)
Comment 6 Ken Sharp 2010-08-13 09:28:41 UTC 
Since revision 11071 (approximately) Ghostscript now uses the FreeType engine for font interpretation and rasterisation by default. As a result this code is not usually used.

We are temporarily retaining it for backward compatibility (should anyone find a problem with the FreeType integration they will be able to switch back) but will eventually remove it from the code base.