Comment 14 for bug 960666

> Is this the definitive solution now? Should I release cups-filters 1.0.8?

I just can't answer that. We're working around a bug in a version of the Brother Postscript implementation, with no access to the internals of the interpreter. My *best guess*, based on the testing we've done, is that there is some problem with the interaction of multiple compression filters in the same filter chain, so I'm suggesting we remove the opportunities for multiple compression filters to be used in the same chain - the only case remaining where this could happen is the color image case - hence adding "-dEncodeColorImages=false". (NOTE: this is separate from the CCITT Group 4 filter problem, which is definitely broken in it's own right.)

However, without being able to debug the interpreter code, I can't say byond doubt that the above *is* the problem.

And I certainly can't say that there aren't any more bugs in Brother's code.

I assume we've missed the beta 2 deadline, so it might be worth holding off dong a cups-filters 1.0.8 for a day or so, in case we find a workaround for the HP issue.

Chris