Wireshark mailing list archives

Re: [Wireshark-commits] rev 45660: /trunk/ /trunk/: print.ps


From: "Maynard, Chris" <Christopher.Maynard () GTECH COM>
Date: Fri, 19 Oct 2012 14:54:17 -0400

-----Original Message-----
From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-
bounces () wireshark org] On Behalf Of Gerald Combs
Sent: Friday, October 19, 2012 2:25 PM
To: wireshark-dev () wireshark org
Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 45660: /trunk/
/trunk/: print.ps

Should we still be in the business of generating PostScript output by
hand? Early on it was necessary because the GTK+ printing system was
primitive. However, the current versions of GTK+ and Qt both offer
high-level printing APIs that should be able to generate PostScript,
PDF and other output formats for us.

If there's a better way, then we should probably take advantage of it.  Maybe file a bug report for it though as this 
is probably not a high priority item judging by the fact that this bug has been around for over 2 years now, so it 
doesn't seem like a lot of people are generating PostScript output or it would have been noticed before now.

On 10/19/12 11:05 AM, cmaynard () wireshark org wrote:

http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=45660

User: cmaynard
Date: 2012/10/19 11:05 AM

Log:
 Add back the "%!" removed in r33773; otherwise, for some unknown
reason, only 1 page will be viewable.  (Tested w/gsview 5.0 and
ghostscript 9.06)  #BACKPORT(1.8, 1.6)

Directory: /trunk/
  Changes    Path          Action
  +1 -0      print.ps      Modified


OK, section 3.2 of http://partners.adobe.com/public/developer/en/ps/5001.DSC_Spec.pdf explains why the "%!" header 
comment is needed in our case.

-- 

CONFIDENTIALITY NOTICE: The information contained in this email message is intended only for use of the intended 
recipient. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, 
distribution or copying of this communication is strictly prohibited. If you have received this communication in error, 
please immediately delete it from your system and notify the sender by replying to this email.  Thank you.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

Current thread: