[gs-bugs] [Bug 689851] Portions of output missing

[bugs.ghostscript.com-bugzilla-daemon at ghostscript.com]

http://bugs.ghostscript.com/show_bug.cgi?id=689851





------- Additional Comments From marcos.woehrmann at artifex.com  2008-05-18 23:51 -------
I believe r7988 is the is the revision which "broke" this file:

r7988 | henrys | 2007-05-20 23:40:28 -0700 (Sun, 20 May 2007) | 48 lines

Back out the changes associated with 7715 and 7773.  This fix is
probably wrong, it only masks an underlying problem by disabling high
level images and it slows down many jobs.  I believe the problem was
misunderstood from the outset but I don't clearly understand the svn
change log, it reads:

   Fix for banding of some images not matching non-banding output.
   Added check for an invariant that the translation matches in the 
   two matrixes used in rendering.  In this case the non-high level image
   path is taken.  A better solution would be to a single matrix, as this will
   increase the display list size for some files.

It is not clear what "single matrix" means.  There is one ctm
associated with the image and one associated with the graphics state,
both must be used by either the high level image code or the default
image machinery.  The change checked that graphics (imager) state ctm
translation components matched the translation components that map
image space to device space.



marcos at imac:[75]% svn diff -r7987:7988
Index: src/gxclimag.c
===============================================================
====
--- src/gxclimag.c	(revision 7987)
+++ src/gxclimag.c	(revision 7988)
@@ -376,9 +376,6 @@
 	varying_depths ||
 	(code = gs_matrix_invert(&pim->ImageMatrix, &mat)) < 0 ||
 	(code = gs_matrix_multiply(&mat, &ctm_only(pis), &mat)) < 0 ||
-	/****** CAN'T HANDLE SOME TRANSFORMS ******/
-	(mat.tx != cdev->imager_state.ctm.tx) ||  
-	(mat.ty != cdev->imager_state.ctm.ty) ||  
 	!(cdev->disable_mask & clist_disable_nonrect_hl_image ?
 	  (is_xxyy(&mat) || is_xyyx(&mat)) :
 	  image_matrix_ok_to_band(&mat))








------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.