| Product PDF Handshake | 
| Version 2.0.0 | 
| Prerequisites none | 
| Supersedes u0236, u0232 | 
| Problem-No 350, 358, 377, 613 | 
| Date Fri Nov 16 16:23:12 MET 2001 | 
| Files sgi:lib/libpdf_s.sosol4:lib/libpdf_s.so
 alpha:lib/libpdf_s.so
 dg86:lib/libpdf_s.so
 linux:lib/libpdf_s.so
 hppa:lib/libpdf_s.sl
 rs6000:lib/libpdf_s.a
 rhappc:lib/libpdf_s.a
 | 
| Architectures sol4 rs6000 sgi hppa alpha dg86 linux rhappc | 
| Subject wrong color conversion for DeviceN colors | 
| Info The conversion from DeviceN colors to the alternate color spacecould produce wrong values if the DeviceN color space used a PDF
 Type 4 function, resulting in wrong colors for layout images and
 composite printing.
 Also fixed:
 - Overprint/knockout did sometimes work incorrectly if the
 overprint mode in the contents stream of a page was changed
 without changing the color.
 - The conversion of embedded CFF (compressed Type 1) fonts did
 fail if the fontname used in the PDF file was different from
 the fontname used in the CFF file. The problem occured with
 PDF files generated by Adobe InDesign.
 - For PDF documents containing both shadings and CID keyed fonts,
 printing/layouting could fail with the error message "Unknown
 token" or "Internal error, CID not found".
 - Conversion of a TrueType font with a format 2.0 'post' table
 could produce wrong glyphs or core dumps.
 - Setting a color on a page without setting a color space first
 did cause a core dump instead of using the default color space
 DeviceGray.
 |