public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: John <valhalla@computerdatasafe.com.au>
To: blinux-list@redhat.com
Subject: Re: SpeechBox
Date: Tue, 29 Oct 2002 10:41:55 +0800	[thread overview]
Message-ID: <200210291041.55952.valhalla@computerdatasafe.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0210281644200.20679-100000@localghost.localdomain>

Some time ago when VV on Linux was new, I was on the VV list.

Viavoice for Linux was only release with American English. The IBM folk on the 
list said, "Substituting other dictionaries probably will work, but is 
unsupported."

The source of other dictionaries was VV for Windows - a friend's computers or 
(for those who speak with English or Australian accents) the Windows Viavoice 
SDK on the IBM website.

UK English and German in particular were mentioned as "probably working," but 
the implication was there that many other languages would work too.


On Monday 28 October 2002 23:48, Tobias Vinteus wrote:
> Wait a moment, I thought ViaVoice could only speak American English. 
> Is this trickery documented somewhere or could someone please explain it 
> to me? Is it possible to make it speak even more languages?
> 
> /Tobias
> 
> On Fri, 25 Oct 2002, Mario Lang wrote:
> 
> > Er, you know that you can convince viavoice to speak french, do you?
> > 


-- 


Cheers
John.

Please, no off-list mail. You will fall foul of my spam treatment.
Join the "Linux Support by Small Businesses" list at 
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb





      parent reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 SpeechBox Nath
 ` SpeechBox Mario Lang
   ` SpeechBox Nath
     ` SpeechBox Mario Lang
       ` SpeechBox Nath
       ` SpeechBox Nath
       ` SpeechBox Tobias Vinteus
         ` SpeechBox Mario Lang
         ` John [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=200210291041.55952.valhalla@computerdatasafe.com.au \
    --to=valhalla@computerdatasafe.com.au \
    --cc=blinux-list@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).