[Guy Harris <gharris@xxxxxxxxx>]

Ulf Lamping wrote:

> No. We won't ship two different versions with the same 0.10.12 version 
> number. That's simply a very bad idea.

He could perhaps get a buildbot snapshot if we do a fix - but that, of 
course, won't be "0.10.12 with that changed", as it'd include other 
changes as well.

(The right long-term fix is probably to add a "print object" 
implementation - see print.c - that directly uses the Win32 print APIs, 
and, in the Win32 version of Ethereal, use that when printing, rather 
than printing to a temporary file and then reading the file and using 
the Win32 print APIs to print its contents.  That'd fix the problem by 
not *having* a temporary file....

If we implement all the methods for that object, including "new_page", 
that'd also fix a bug in the old SourceForge Ethereal bug database, 
wherein form feeds aren't printed correctly when doing Windows printing.

If not all print operations use the print.c code, we should fix the ones 
that don't already do so to use that code.  If that requires more 
methods to be added to print objects, we should do that.

The truly ambitious could add methods for graphical printing as well, 
letting us print out various graphical displays; it could generate 
PostScript on UN*X, although eventually it might be interesting to, when 
Ethereal can be built for KDE or GNOME, rather than just GTK+, use those 
environments' print mechanisms.)