Bug 692004 - Text rendering mode 3 ingnored for high resolutions
Summary: Text rendering mode 3 ingnored for high resolutions
Status: RESOLVED FIXED
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: General (show other bugs)
Version: 9.00
Hardware: PC Windows 7
: P4 normal
Assignee: Chris Liddell (chrisl)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-27 21:26 UTC by Zoltán
Modified: 2011-03-23 13:45 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---

Attachments
text rendering mode = 3 (9.04 KB, application/pdf)
2011-02-27 21:28 UTC, Zoltán 		Details
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 Zoltán 2011-02-27 21:26:57 UTC 
Attached PDF contains a text with rendering mode = 3 (invisible). 

This parameter is ignored when resolution is set too high (e.g. 1200 dpi or over) – that is, the text is shown in its original color (orange).

For lower resolutions (e.g 200 dpi) the file renders as expected (no visible text). 

Command line:

gs -r1200 -dNOPAUSE -dBATCH -sDEVICE=tiffsep -sOutputFile=%1.%%03d.tif %1
gs -r200 -dNOPAUSE -dBATCH -sDEVICE=tiffsep -sOutputFile=%1.%%03d.tif %1
Comment 1 Zoltán 2011-02-27 21:28:02 UTC 
Created attachment 7295 [details]
text rendering mode = 3
Comment 2 Chris Liddell (chrisl) 2011-03-17 09:56:51 UTC 
The problem was caused by glyphs being rendered uncached, and thus bypassing the "normal" method of avoiding imaging glyphs in rendering mode 3.

I've added a check where uncached glyphs are rendered, so that the marking operation is "short circuited" for rendering mode 3, but the current point is still correctly updated.

fixed in r12299.
Comment 3 Zoltán 2011-03-23 13:19:23 UTC 
May you give a link to the implemented changes, please?
Comment 4 Chris Liddell (chrisl) 2011-03-23 13:45:31 UTC 
Sorry, here's the link for the commit:
http://ghostscript.com/pipermail/gs-cvs/2011-March/012492.html


I need to assess whether a similar change is needed for fonts with PaintType 2 - if they do, I'll update this bug with the information.