Summary: | (pdfwrite) composite font with Type 3 descendent | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | Igor Melichev <igor.melichev> |
Component: | PDF Writer | Assignee: | leonardo <leonardo> |
Status: | NOTIFIED FIXED | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | master | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Customer: | Word Size: | --- |
Created attachment 493 [details]
020-01-.ps
Attaching a reduced test.
*** Bug 688221 has been marked as a duplicate of this bug. *** Patches to HEAD : http://ghostscript.com/pipermail/gs-cvs/2006-January/006252.html http://ghostscript.com/pipermail/gs-cvs/2006-January/006253.html *** Bug 687875 has been marked as a duplicate of this bug. *** One more patch to HEAD : http://ghostscript.com/pipermail/gs-cvs/2006-January/006255.html |
Type 3 descendent of a composite font and all subsequent characters of the text are converted into a bitmap font. This happens due to pdf_text_set_cache tries to encode a character with penum->orig_font and fails. The problematic code is gdevpdtt.c ln 118. Instead that it must use penum->current_font and penum- >returned.corrent_glyph, because pdfwrite should decompose the composite font into descendents. Test cases are the 2dn string in the box 020-08 in 020-01.ps, and 093-01.ps .