9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] scanner support
Date: Mon, 23 Jul 2001 06:51:13 +0100	[thread overview]
Message-ID: <E15OYcb-0004iP-0A@finch-post-10.mail.demon.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 613 bytes --]

Whether TWAIN really stands for that is reaching urban myth status.

www.twain.org used to say that it doesn't stand for anything, which
sounded like an organisation wanting to forget an embarassing past.
Now they say that it is derived from the expression "and never the
twain shall meet", and that a contest was held retrospectively to
find an acronym. They didn't like any of the suggestions, but
Technology Without An Interesting Name was one of the entries
and it has haunted them ever since. They quote the Free Online
Dictionary of Computing for added emphasis.

http://www.twain.org/faq.htm


[-- Attachment #2: Type: message/rfc822, Size: 1329 bytes --]

From: Jonathan Sergent <sergent@IO.COM>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] scanner support
Date: Sun, 22 Jul 2001 19:50:31 -0700
Message-ID: <20010723025152.B78B1199EB@mail.cse.psu.edu>

>(I think the name `TWAIN' has something to do with this).

TWAIN == "Technology without an interesting name" (seriously)

For what it's worth, photopc works fine under APE for getting images
off of many types of digital cameras (over serial interfaces, not USB).

             reply	other threads:[~2001-07-23  5:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-23  5:51 nigel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-26  2:58 David Gordon Hogan
2001-07-23 19:58 Richard Miller
2001-07-23 13:56 anothy
2001-07-23  2:50 Jonathan Sergent
2001-07-23  2:35 David Gordon Hogan
2001-07-23 15:06 ` Douglas A. Gwyn
2001-07-22 19:45 anothy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E15OYcb-0004iP-0A@finch-post-10.mail.demon.net \
    --to=nigel@9fs.org \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).