From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <80c90c50264d433c9b2e4b74b10bc072@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] TODO lists for Plan 9
From: Charles Forsyth <forsyth@terzarima.net>
Date: Tue, 13 Jul 2004 10:04:05 +0100
In-Reply-To: <7697b982eca0d2ba56b0c1f05a4b07f8@9netics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: bf60c2ec-eacd-11e9-9e20-41e7f4b1d025

TWAIN is a (rather elaborate) software interface, for applications to use,
paired with a device-specific target driver that does the translation
between TWAIN requests and the device's own protocol, and
never the twain shall meet, so knowing TWAIN does not guarantee being
able to talk to any given device.   you still need a driver from the manufacturer,
in general.  thus, for a system such as Plan 9, one might as well design a
reasonable interface to such things.

as a `union' interface, TWAIN is so big and complicated
I'd be somewhat surprised if there were many
devices that implemented most of it directly.