[27263] in Athena Bugs
Re: hexagons go awry on w20color
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Tue Dec 16 19:11:49 2008
Message-Id: <AFD2D0C4-8F79-428E-96B3-1AAE32E548FC@mit.edu>
From: Jonathan Reed <jdreed@mit.edu>
To: John Hawkinson <jhawk@mit.edu>
In-Reply-To: <200812162340.mBGNeZcl003978@portnoy.mit.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 16 Dec 2008 19:11:33 -0500
X-Spam-Flag: NO
X-Spam-Score: 0.00
Cc: bugs@mit.edu
Errors-To: bugs-bounces@mit.edu
[bug-print dropped, because I sent them mail about this last week]
After OLC received (via Copytech staff) numerous reports of people
being unable to print to w20color, I did some testing last week. I
was not able to reproduce any of the problems reported by Copytech
folks, and the problems we've seen tend to involve large (both in page
count and file size) documents.
The other major problem I discovered was that PDFs submitted from
Acroread to the queue w20color2 only print the header page, and
nothing else. (The printer insists that that it has nothing left to
print.) However, prepending the following PostScript to the file:
%%BeginFeature *Duplex True
<< /Duplex true >> setpagedevice
%%EndFeature
And sending it directly to raw@w20color.mit.edu works just fine. I
found this baffling, as I thought that's what the duplex queues did.
I did not have time to test other types of jobs submitted to the
duplex queue from other applications.
I suspect the printer has far more problems with PostScript. Perhaps
someone who speaks PostScript would be willing to craft a test
document or a series of test documents to attempt to figure out what
works and what doesn't.
-Jon
On Dec 16, 2008, at 6:40 PM, John Hawkinson wrote:
> On w20color, the hexagon cover sheet prints incorrectly.
> Instead of printing as hexagons, e.g.:
>
> ------
> / \
> / \
> \ /
> \ /
> ------
>
> Instead they print more like:
>
>
> ------ /
> / /
> _____\/ \/
> /\ /\
> \ \
> ------ \
>
> Kind of weird. I worry that other postscript could go awry?
>
> --jhawk
