Code their printer drivers correctly and they wouldn't have to.
That isn't helpful at all.
I'm sorry, but I've bitten my tongue long enough (along with everyone else I suspect), I'm going to have to speak up.
We have here a known problem, now acknowledged by the vendors involved ( Adobe public statements, Apple printing engineer postings on Dev forums ), tested and confirmed by the engineers working for those vendors ( Eric Chan of Adobe ) and by industry players of some "repute" ( Jeff Schewe, Andrew Rodney, Mark Dubovoy ) who have privileged access to information and people who are in a position to know more than anyone ( i.e. the engineers who have access to the actual code ). All of the above working to achieve a resolution to this problem as quickly as possible.
On the other hand we have "random internet forum dude" ( DYP ) who insists they are all wrong and he is right, provides no evidence to support his conclusions and clearly has an axe to grind with a particular vendor.
Doyle, for someone who (claims he) is not affected by this problem, you've made more posts on these threads than anyone else, many of which are in essence "well mine works, you just bought the wrong printer, VendorX is rubbish".
I think most of the people here are interested in resolving a problem which is affecting them and causing problems to their work and business, as opposed to providing an audience for your agenda.
Please try to be constructive...