From: carl.lowenstein@gmail.com (Carl Lowenstein)
Subject: [TUHS] UNIX/32v & speak....
Date: Mon, 26 Oct 2009 10:44:02 -0700 [thread overview]
Message-ID: <5904d5730910261044g524b1c11i71f34a1de5c1cab6@mail.gmail.com> (raw)
In-Reply-To: <46b366130910261029g52e47beavf1011a123d5839c4@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
On Mon, Oct 26, 2009 at 10:29 AM, Jason Stevens <neozeed at gmail.com> wrote:
> I was going to upload the various man pages of 32/V so I'd have a 'nice'
> collection of them, and to help with my eventual conversion of the help text
> into RTF for a windows helpfile when I was reading through the number
> command...
> http://gunkies.org/wiki/32v_1m_number
>
>> Number copies the standard input to the standard output, changing each
>> decimal number to a fully spelled out version. Punctuation is added to make
>> the output sound well when played through speak(1).
>
> So it seems that VAX's could do audio at some point? Does anyone know how
> it worked? Naturally the speak command seems to be missing, but it does
> seem very interesting...!
See "Votrax" in Wikipedia for more information. "Vocal division of
Federal Screw Works".
A speech synthesizer, predecessor of Digital's DECtalk.
> I wonder if this was the start of the UNIX/IVR relationship....?
What's IVR?
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenstein at ucsd.edu
_______________________________________________
TUHS mailing list
TUHS at minnie.tuhs.org
https://minnie.tuhs.org/mailman/listinfo/tuhs
prev parent reply other threads:[~2009-10-26 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 17:29 Jason Stevens
2009-10-26 17:40 ` John Cowan
2009-10-26 21:51 ` Ian King
2009-10-26 17:44 ` Carl Lowenstein [this message]
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=5904d5730910261044g524b1c11i71f34a1de5c1cab6@mail.gmail.com \
--to=carl.lowenstein@gmail.com \
/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).