Bug#1003255: No

[Peter Müller <PeterMueller@ro.ru>]

tags 1003255 - wontfix
severity 1003255 normal
thanks


It's not the presence or absence of any such check that makes it into a 
bug.  It's the resulting behavior that has a bug.

E.g., you could implement this by checking at the beginning of the 
document whether the information in the aux file says the opacity code 
should be emitted.  If so, emit the code and set a Boolean macro, say, 
“\transparencyCodeWritten” to “true”, otherwise to “false”.  Then, 
whenever a transparency/opacity-related operation is encountered, test 
whether “\transparencyCodeWritten” is still “false” and if so, emit the 
transparency/opacity-related code to the output if possible immediately 
(I don't now Postscript enough to say this) and set 
“\transparencyCodeWritten” to “true”.  If not possible immediately, 
write a flag info the aux file to be read at the next LaTeX run.

There might be other ways to repair this.

If a user such as you or me or (or even user187802, even if they are the 
current maintainer) refuses to implement this, it's his or her right 
(since it's all done in free, unpaid time, and only very few people 
worldwide have it), but this doesn't make the current behavior less 
erroneous.  Maintainers and users come and go, and PStricks stays.

P.