diff options
author | Chris Liddell <chris.liddell@artifex.com> | 2011-12-09 10:01:57 +0000 |
---|---|---|
committer | Chris Liddell <chris.liddell@artifex.com> | 2011-12-09 10:17:00 +0000 |
commit | 9a2555a91fbc2fa73a6e2f8f4035b58b4ff5ae57 (patch) | |
tree | 158847389dddf0044a2027f877d2de782e3fafd7 | |
parent | 5359a2d0bf10568102f85d797a91c0595518ae23 (diff) |
Bug 692686: use same scan conversion settings for "clip" as for "fill"
The PDF job in question renders most of its text as simple text render mode 0,
but about three glyphs are done using tr mode 7, and showing an image through
the resulting clip.
The problem is that when we image a glyph, we use fill_adjust 0 (rather than the
default of ~0.3), otherwise glyphs are overly bold. When using one of the clip
text modes in PDF, however, we still used the default fill_adjust, which
resulted in an overly "bold" clip path.
This causes a number of cluster differences: several are progressions, the
others are pixel differences - mostly cases where resolution and/or zoom level
affect whether we precisely match Acrobat.
-rw-r--r-- | gs/Resource/Init/pdf_ops.ps | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gs/Resource/Init/pdf_ops.ps b/gs/Resource/Init/pdf_ops.ps index 03a745375..4d3b4e191 100644 --- a/gs/Resource/Init/pdf_ops.ps +++ b/gs/Resource/Init/pdf_ops.ps @@ -594,7 +594,7 @@ end readonly def matrix /TextTempMatrix gput % see settextposition } bdef /ET { - TextRenderingMode 4 ge { clip newpath } if + TextRenderingMode 4 ge { .currentfilladjust 0 .setfilladjust clip newpath .setfilladjust} if TextSaveMatrix setmatrix currentdict /TextSaveMatrix undef } bdef |