Hi,

Am 25.10.2010 14:28, schrieb José Rodolfo Carrijo de Freitas:
Adam,
You were right. With the last solution I would hit objects which were not 
guaranteed to be an image.
However, the font problem is a different one...
I was wondering if the remaining operators which identifies image graphical 
states would affect fonts and texts operators.
A graphics state isn't limited to images. All other operators are also part of 
a gs.

Accordingly with the spec, they wouldn’t affect. However if they work at a 
stack (and it seems they do), probably it is interfering in some manner.
You shouldn't remove the q/Q operator, otherwise the stack holding the graphics states may be in a mess.

I took a look with pdfdebugger on both streams(the original one, and the edited 
one) comparing them. It seems to be exactly as it should, excepts for some 
differences in float numbers and the image operator (with its name) which I 
extracted, yet, they print differently. I believe There are some problems in 
graphics state.

http://b.imagehost.org/view/0930/comparing-pdfs

What kind of problem that seems to be?
It looks like an unwanted scaling. Did you remove one or more of the q/Q 
operators?

BR
Andreas Lehmkühler

Reply via email to