Number: 456

Date:  2-Apr-84 11':49':01

Submitter: Sannella.PA

Source: Stansbury.pa

Subject: HARDCOPYW producing bad press files

Lisp Version: 

Description: '
Date': 31 Mar 84 17':53 PST'
From': Stansbury.pa'
Subject': Lisp': Hardcopyw to file will not empress'
To': LispSupport.pa'
cc': Stansbury.pa, Hausladen'
Lisp-System-Date': 29-Mar-84 17':34':40'
Machine-Type': Dorado'
'
(HARDCOPYW (WHICHW) ''FOO) followed by (EMPRESS ''FOO) breaks saying that foo is a press file with a non-integral number of pages.  Yuk.'
'
-- Tayloe.'
'
-----'
'
Date':  2 Apr 84 12':13 PST'
From': Kaplan.pa'
Subject': Re': AR 456': HARDCOPYW producing bad press files'
In-reply-to': LispSupport.pa''s message of 2 Apr 84 11':49':42 PST (Monday)'
To': LispSupport.pa'
cc': Kaplan.pa'
'
I do not really understand the HARDCOPYW interface.  Problems on this should be given to Masinter.  Nuyens also looked into this recently, perhaps he should be included.'
'
I think that there are some serious design flaws in here, and also in the Printertypes interface.  Larry and I had different conceptions of the way it should be, and the result probably fell somewhere in the middle.'
'
All that aside, I wouldn''t be surprised if this problem is due to the fact that HARDCOPYW is somehow constructing an Interpress file, but then attempting to print it as a press file, perhaps because the extension of the file is .PRESS.'
'
Right now, Gregg might be the best bet for this.'
'
--Ron'
'
-----'
'
Date':  2 APR 84 13':23 PST'
From': JONL.PA'
Subject': Re': AR 456': HARDCOPYW producing bad press files'
To':   Kaplan, LispSupport'
cc':   JONL, Nuyens'
'
In response to the message sent   2 Apr 84 12':13 PST from Kaplan.pa'
'
Many months ago I complained that HARDCOPYW was arbitrarily producing an'
Interpress file, even though the first printer on my DEFAULTPRINTINGHOSTS'
was a press printer.  The lossage, of course, is that the nearest Interpress'
printer is a loooong walk, and a floor hop away; whereas the press printer'
is "just around the corner".'
'
-----'
'
Date': 31 May 84 17':30 PDT'
From': Masinter.pa'
Subject': AR#456, HARDCOPYW and press vs interpress'
To': Nuyens, Stansbury, Hausladen, Kaplan, JonL'
cc': LispSupport'
'
I dunno if I sent out a message about this before. I added a while back a PRINTERTYPE argument to HARDCOPYW so you could say what kind of printer you were preparing a file for.'
'
In addition, I''ve now made PRINTFILETYPE try harder to recognize the file type; that is what EMPRESS used to decide what kind of printer to send the file to. So': what you tried before will work (and produce and print an Interpress file), and you can also explicitly tell HARDCOPYW to make a press file by giving PRESS as the PRINTERTYPE argument.'
'
-----'
'
Date': 31 May 84 21':41 PDT'
From': JonL.pa'
Subject': Re': AR#456, HARDCOPYW and press vs interpress'
In-reply-to': Masinter.pa''s message of 31 May 84 17':30 PDT'
To': Masinter.pa'
cc': Nuyens.pa, Stansbury.pa, Hausladen.pa, Kaplan.pa, JonL.pa, LispSupport.pa'
'
I may (or may not) remember a message from some time back, but didn''t specifically connect it to this problem.  I wonder':'
  1) Could the "Hardcopy" command in the "Paint" menu be extended to'
     utilize this new argument to HARDCOPYW?  Maybe have the existing'
     "Hardcopy" command stay the same, but another "PressHardCopy" '
     which would try to "press out" the window (rather than interpress).'
  2) What happens if the window can''t be fit into the format described'
     by the PRINTERTYPE argument?  So far, I''ve tried it out on several'
     of the windows that randomly appear on my screen, and haven''t had'
     any that Expresso barfed on.'
'
-- JonL --'
'
-----'
'
Date':  1 Jun 84 16':51 PDT'
From': masinter.pa'
Subject': Re': AR#456, HARDCOPYW and press vs interpress'
In-reply-to': JonL.pa''s message of 31 May 84 21':41 PDT'
To': JonL.pa'
cc': Masinter.pa, Nuyens.pa, Stansbury.pa, Hausladen.pa, Kaplan.pa, LispSupport.pa'
'
Most users out in the world are lucky to have one printer. I''m reluctant to add to the default user interface a lot of complexity that only we at Xerox need. Maybe it is a local Lispusers package to add the complexity to HARDCOPYW''s menu interface. I''m more willing to add the hooks necessary to implement such a lispusers package gracefully, although I think merely advising HARDCOPYW would do it well enough.'
'


Workaround: 

Test Case: 

Edit-By: Sannella.PA

Edit-Date: 17-Aug-84  9':38':14

Attn: 

Assigned To: Nuyens

In/By: Harmony

Disposition: HARDCOPYW now takes a PRINTERTYPE argument where you can supply what kind of printer it is. Also, PRINTFILETYPE now tries harder to find out what kind of file it is; EMPRESS uses PRINTFILETYPE to tell.

System: Windows and Graphics

Subsystem: Printing

Machine: 

Disk: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Difficulty: Moderate

Frequency: Everytime

Impact: Serious

Priority: Hopefully

Status: Closed

Problem Type: Bug

Source Files: