I do not get the same error as you. But I guess you do different. Please show exactly what you do. And please put that between CODE tags as I did (Posting in Code Tags - A Guide).
On 2011-06-10 21:06, hcvv wrote:
>
> Thanks for the clarification. I am not an expert at all here, but let us
> hope that this triggers someone who knows more.
I believe it is a postscript error, detected by the printer itself, so the
printer model is also relevant. And he needs an expert in postscript.
I would generate, not print, the output file for both encodings, and
compare them. Possibly the Spanish one is incorrect, so a Bugzilla is in
order. Or, he could post to the mail list, the maintainer of the printer
stack will probably answer - if the post has the pertinent info
Also, the ps output could perhaps be cleaned with ps2ps, and then
resubmitted to the printer.
And the file “/tmp/text.rpt” could also be relevant.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Thank you for your help Carlos, using ps2ps printed my report but it was just moved a little bit, but after read the gs man page I found that what that command does is just change the postscript level so what I actually did was run my enscript script with leve1 of postcript and that printed my report just how I need it.