Bug 688378

Summary: Multimedia links do not render properly
Product: Ghostscript Reporter: Matias Gertel <matias>
Component: PDF InterpreterAssignee: Alex Cherepanov <alex>
Status: RESOLVED FIXED    
Severity: major    
Priority: P3    
Version: 8.53   
Hardware: Macintosh   
OS: Linux   
URL: http://www.digitalarena.co.nz/test/Women%20in%20Transportation.pdf
Customer: Word Size: ---
Attachments: This is an example PDF, have a look at the multimedia links

Description Matias Gertel 2005-11-13 13:26:03 UTC 
I've just installed 8.53 using a standard ./configure, make, make install... no flags set.
The first PDF I tested was the "Women in Transportation.pdf" which is included as part of the InDesign CS 
1 examples. I've used this pdf as a test on 8.14 and up and this is the first release that breaks it...
Comment 1 Matias Gertel 2005-11-13 13:32:06 UTC 
Created attachment 1766 [details]
This is an example PDF, have a look at the multimedia links
Comment 2 Dan Coby 2005-11-15 16:45:19 UTC 
Looks okay to me.  What specifically is wrong?
Comment 3 Matias Gertel 2005-11-15 17:26:05 UTC 
Sorry, should have given more information... my fault...
If I try this:
gs -sDEVICE=png16m -dGraphicsAlphaBits=4 -dTextAlphaBits=4 -dBATCH -dNOPROMPT -dNOPAUSE -
r144 -q -dFirstPage=1 -dLastPage=1 -sOutputFile="test.png"  -f "Women in Transportation.pdf"
It renders wrong (the little movie and sound icons are broken)
but if I take the -dGraphicsAlphaBits=4 out, or set it to 1 then all seems fine...
Now, I know the documentation sais this might happen, but earlier versions of gs used to handle this file 
correctly...
Hope this helps!
Comment 4 Ray Johnston 2005-11-16 16:28:47 UTC 
I agree that the movie (purple film reel) icons and sound (yellowish speaker)
icons are rendered strangely.

It is clearly an interaction with the transparency and the 'trick' used to
render graphics with anti-aliasing.
Comment 5 Matias Gertel 2006-03-22 12:13:06 UTC 
*** Bug 688607 has been marked as a duplicate of this bug. ***
Comment 6 Alex Cherepanov 2008-12-21 14:14:01 UTC 
This problem has been fixed since v. 8.54.