Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 UW 5/3/83; site uw-beaver
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!houxm!vax135!cornell!uw-beaver!info-mac
From: info-mac@uw-beaver (info-mac)
Newsgroups: fa.info-mac
Subject: Re: QD Text Transfer Modes
Message-ID: <2027@uw-beaver>
Date: Thu, 25-Oct-84 21:34:22 EDT
Article-I.D.: uw-beave.2027
Posted: Thu Oct 25 21:34:22 1984
Date-Received: Fri, 26-Oct-84 09:30:33 EDT
Sender: daemon@uw-beave
Organization: U of Washington Computer Science
Lines: 26

From: Reed.SoftArts@MIT-MULTICS.ARPA
Local:  Thomas.Newton at CMU-CS-SPICE,info-mac at SUMEX-AIM
Original-Date:  24 OCT 1984 17:03:52
Resent-Date: Thu 25 Oct 84 16:53:47-PDT
Resent-From: Ed Pattermann <PATTERMANN@SUMEX-AIM.ARPA>
Resent-To: ;@info-mac

Not to quibble, but what would srcCopy mode mean in Text calls?

How much of the bounding box would be blanked?  If there is
intercharacter spacing that is not present in the font
(presumably compressed out, a la the Xerox Strike format) would
that not be obliterated?

I agree that graphics packages should be general, but that
doesn't mean a mode that doesn't make sense should be
implemented?

If I were to define srcCopy, I might want it to blank only the
interior of letters (who says that characters are in bounding
RECTANGLES anyway) or just within the tightest convex polygon,
or in a rectangle that just barely enclosed the black bits of
each character.  As I said in previous mail, the idea that
monospacing crts without overstrikes are sacred cows shows the
tendency of many programmers (not all, thank god) to be
obsessive compulsive neurotics.