Comment 23 for bug 1049635

I can't see any way to reproduce the page description accurately without running into the same problem.

IIRC, some Windows Postscript drivers have the option to produce the page as an image, which I believe is intended to work around this type of issue. Thus reducing the PDL complexity, for such limited printers, at expense of comms traffic.

I'm intrigued by Till's results with the HP because, as I stated above, the path(s) in question, whether they are explicitly described in the PS, or result from character outlines are equivalent in complexity at the time the printer executes the clip operator.

I would expect it to always be slow, because making marks through such a hugely complex clipping path is a very time consuming operation.

Sorry the news isn't better.