Bug 692528 - Wrong print copies number
Summary: Wrong print copies number
Status: RESOLVED INVALID
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: General (show other bugs)
Version: master
Hardware: PC Windows XP
: P4 normal
Assignee: Default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-22 07:43 UTC by XIN
Modified: 2011-10-10 09:44 UTC (History)
0 users

See Also:
Customer:
Word Size: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description XIN 2011-09-22 07:43:19 UTC
Open a 1-page document.
If you print it with any number of copies, you'll get 1 page output anyway.

Is this known issue?
Comment 1 Marcos H. Woehrmann 2011-09-22 17:10:00 UTC
We are going to need some more information:

1.  What version of Ghostscript are you using?

2.  What device are you writing to?

3.  A sample file and command line would be nice.
Comment 2 XIN 2011-10-10 03:00:26 UTC
http://www.pdfforge.org/files/old_forum/1013.html

It said Ghostscript can't handle such files.
Comment 3 Ken Sharp 2011-10-10 07:01:16 UTC
(In reply to comment #2)
> http://www.pdfforge.org/files/old_forum/1013.html
> 
> It said Ghostscript can't handle such files.

Quoting a 4 year old comment on a non-Ghostscript site isn't helpful. Please supply the information requested in comment #1.
Comment 4 XIN 2011-10-10 08:44:03 UTC
Ghostscript : v9.04
device : PDFCreator v1.2.3
When I print a MS-Word file (.doc) which has only one page to the PDFCreator with copies set to 3, I got only one copy. While another doc file 2 pages and 3 copies, I got 3 copies correctly.
I don't know which one cause the problem, PDFCreator or Ghostscript ? 
I found this: http://www.pdfforge.org/files/old_forum/1013.html. It said Ghostscript can't handle such files. I want to know is it right?
Comment 5 Ken Sharp 2011-10-10 09:44:39 UTC
(In reply to comment #4)
> Ghostscript : v9.04
> device : PDFCreator v1.2.3

That is not a Ghostscript device. There are a number of applications with that name, its possible this one leverages off Ghostscript (several do). But you haven't given us any reason to think this is the case.

We can't, and don't, support other people's applications.


> When I print a MS-Word file (.doc) which has only one page to the PDFCreator
> with copies set to 3, I got only one copy. While another doc file 2 pages and 3
> copies, I got 3 copies correctly.

The pdfwrite device ignores /#copies and /NumCopies. What would be the point in creating a PDF file with multiple identical pages ? When you print the PDF file to a physical printer, then you want the number of copies to be set.

I am unable to comment on your files, because you haven't supplied them. There are two ways for a PostScript program to print multiple copies, one is to set the /NumCopies or (older versions of PostScript) set /#copies. The other is simply to send the same page description multiple times. My guess would be that one of your files takes one approach and the other file the other approach. But that's pure guesswork.


> I don't know which one cause the problem, PDFCreator or Ghostscript ? 

I have no idea, and you haven't considered the possibility that the PostScritp driver is involved, or that there is in fact no problem. If you cannot provide a Ghostscript command line and a sample PostScript file, then we cannot help you. You could try taking the problem up with the creators of the 'PDFCreator' software. I imagine they will want a specimen file too.


> I found this: http://www.pdfforge.org/files/old_forum/1013.html. It said
> Ghostscript can't handle such files. I want to know is it right?

That depends on the device (device in Ghostscript terms). Some devices ignore the number of copies, others honour it. It certainly is not true that Ghostscript cannot handle /#copies or /NumCopies.

Since you haven't supplied a test file, I can't possibly say if Ghostscript 'cannot handle such files'.

I'm closing this as invalid, if you can supply a Ghostscript command line and a sample PostScript file for us to investigate, then by all means reopen the bug and someone will investigate it.