On Fri, Jul 01, 2005 at 10:28:14AM +0100, Dan Hatton wrote:
On the other hand: as I understand it, the problem Chris has is that his printer is producing the postscript code as text, rather than the picture it represents. I had the same problem, and solved it by _removing_ the "-o raw" that Gimp had put there by default.
Aah, right. Well I also had the same problem and I definitely had to add a -oraw to the options.... but I am printing to a networked cups printer using gimp-print modules in cups (i think, not checked for a while now).
I think that the solution(s) Chris should try would be removing the -o raw if it is there, and if it isn't there then he should try adding it. Quite why this is I do not know :) if I get some spare time later I will investigate and report back to the list.
Thanks Adam