Newsgroups: comp.windows.ms
Path: utzoo!utgpu!watserv1!daemon
From: tom@mims-iris.waterloo.edu (Tom Haapanen)
Subject: Re: Word Perfect -> Word for Windows
Message-ID: <1991Feb17.182435.14497@watserv1.waterloo.edu>
Sender: daemon@watserv1.waterloo.edu
Organization: University of Waterloo, WATMIMS Research Group
References: <5900@mentor.cc.purdue.edu> <cchapman.666566503@romeo> <1991Feb15.173709.6780@eng.umd.edu>
Date: Sun, 17 Feb 1991 18:24:35 GMT
Lines: 23

John R. Burgoyne <burgoyne@eng.umd.edu> writes:
> My big gripe with W4W is that the printer tray, orientation, and paper
> size are outside the scope of the program and are instead part of the
> Windows operating system.

No, they are *NOT* outside the scope of the program.  Any application can
call ExtDeviceMode() or use printer escape codes (such as GETSETORIENT) to
manipulate the printer.  It is only required to conform to the Windows
device-independence guidelines and not muck with the device directly.

That Word for Windows does not support such features reflects only on that
product, not on Windows itself.

> Besides, this doesn't solve the problem of having a document
> associated with a printer and a unique printer port.

Personally, I dislike *this* approach.  To me, a document is just that, and
it should print on any printer to the best of that device's capabilities...
I believe WP's document device-dependency stems from its inability to use
device-independent fonts and attributes...

[ \tom haapanen --- university of waterloo --- tom@mims-iris.waterloo.edu ]
[ "i don't even know what street canada is on"               -- al capone ]
