* Paul E Condon <[EMAIL PROTECTED]> [071023 18:23]: > To make the .ps version, that I refer to in my bug report, I used the > 'print to file' facility in xpdf.
To make sure that it is a problem in gs-* and not in gv, you could also try to convert it using pdf2ps (do not confuse with pdftops, pdf2ps is ghostscript, while pdftops is xpdf) and look with gv at that file. If that has the same problem like looking at the .pdf directly, I'd guess it is gs. (Though I still have not understood the symptoms correctly). > Question: > Clearly, it's unlikely that this bug will be resolved soon. While I'm > waiting I think I would like to continue running gs-gpl because its > error messages will remind me that I need to convert to .ps before > printing. But I am also running CUPS and gs-esp is supposed to have > patches to provide compatibility with CUPS. Should I also convert to > some other print-services manager, if I do decide to continue running > gs-gpl? Or are the compatibility issues not important to a naive user? I don't know much about cups, but reading the history in http://bugs.debian.org/246983 it seems like cups itself would not be effected, but some filters sometimes used with cups might call gs directly instead of gs-esp and thus have problems with the newer gs-gpl not having the extensions needed for cups. (Otherwise you could also change the gs call in gv to gs-gpl or gs-afpl, in my experience gs-esp can break displaying things relatively often.) > The file is 587490 bytes long. I have no web site where I can post > it. Would it be permissible for me to send it to you in an email > attachment? Or can you tell from the error message what is wrong, > and dive into the code on that basis alone? I've no problem with such a large file, but I'm currently guessing it might be a ghostscript problem, and if it is then it would be more important to get it to the ghostscript maintainer once the bug is reassigned. If that file is multiple pages long, you could also try to get a single page displayed incorrectly via pdftk (from package pdftk) with a command like pdftk yourfile.pdf cat 17 output new.pdf to get page 17 (as example). This might also repair some xref tables, so it would be intresting if the result has still the same problem and the same error message. Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
