very now and then a document fails to print and produces a page with the following:
OFFENDING COMMAND: flush
Ther error itslef is no big deal, It's easy to reprint the document.
My problem is with the nearly full ream of paper that follows it, apparently printinng the text of the entire postscript image.
How can I tell the printer to just erase the buffer on this error instead of dumping it to 100 pages of double sided code?
I cannot find a 6300/6350 for reference, but it should be the same as, if not similar, to this:
The vast quantity of these errors are from Fonts. Mostly caused by the move towards mobile output instead of Print. Saving your files to pdf/x will fix it, and be transparent to anyone looking at and using the file.
Simply changes this setting on the driver to what is highlighted here would stop those garbled output jobs.
For whatever reason, printers that have fonts in them, always seem to do the same thing when they get confused as to what font is in the document (All manufacturers I've used). They seem to decide "Hey, this might be Ariel, might not be, but I can't go wrong with Wingdings!" and they convert every letter to Wingdings, which is never going to be the right method.
I found "Postrscript Error Information here:
si I turned if off. BUT, that didn't work. I'll try the softfont option next.
By the way, this is not printing the document with the wrong font. It is literally printing the postscript file to a ream of paper. Here are the first two pages:
I didn't mean to imply it would print the wrong font, sorry.
The biggest (by far) casue of Postscript errors in prints are the fonts themselves being embedded incorrectly. So much so Adobe created the pdf standard for printers (PDF/X) to nearly eliminate these happening. The problem is most designers don't use it, especially now that most consider publication to be for the Web or for Mobile where those things don't matter.
The Softfont thing is just a break-fix where if the output device (printer) can't figure out the font, it wont attempt to "fix" it by replacing it with garbage.
Is there no Page Description Language section on the 6300 web interface?