From: "hank smith" <hanksmith4@earthlink.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: how can I get libXm.so.1 - was Re: software TTS
Date: Wed, 14 Sep 2005 08:46:32 -0700 [thread overview]
Message-ID: <010101c5b943$7bae6020$821a3fce@ron0wrfld8igzk> (raw)
In-Reply-To: <Pine.LNX.4.62.0509141345010.3876@localhost.localdomain>
can you make a rpm or .deb package or something for people who are new to
linux?
----- Original Message -----
From: "Willem van der Walt" <wvdwalt@csir.co.za>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, September 14, 2005 5:35 AM
Subject: Re: how can I get libXm.so.1 - was Re: software TTS
> Hi,
> I have Viavoice outload now working with speakup. I used the old rpms ro
> install viavoice, modified the script runcmdlinespeak, and used the
> generic module of speech-dispatcher to get speechd_up to use it.
> I had to install glibc-2.3.1 and one or two other older libs to get it
> working.
> I also had another viavoice copy which cut off words and is not stable in
> general.
> I moved the compiled version of glibc-2.3.1 onto different machines with
> success. I have tested under Fedora 2 and 3 and Debian.
> HTH
> Willem
>
> On Wed, 14 Sep 2005, Darragh wrote:
>
>> Helo Kenny, I'm not entirely sure where I'm going to get it yet how I
>> have an idea so when I know more I'll let you know.
>>
>> The only lib that I haven't got installed is libXm.so.1. where the hell
>> can I find that. I have libXm.so.3 installed with SuSE but this doesn't
>> seem to work. wouldn't the version 3 of this lib work? would it not have
>> the features of version 1? I've set up a simlink to that lib and called
>> it libXm.so.1 but I'm not sure how to get the rpm to find it.
>>
>>
>> -----Original message-----
>> From: Kenny Hitt kenny@hittsjunk.net
>> Date: Wed, 14 Sep 2005 02:31:06 +0100
>> To: "Speakup is a screen review system for Linux." speakup@braille.uwo.ca
>> Subject: Re: software TTS
>>
>>> Hi.
>>>
>>> So far, I've found my copy of ttsynth to be useless. It appears to be
>>> Viavoice under a new name with few (if any) changes. It still seems to
>>> require outdated libs to get the utilities to run, and there isn't any
>>> documentation on the utilities included.
>>>
>>> My problems could be the seller, so where do you plan to get it?
>>>
>>> Kenny
>>>
>>> On Tue, Sep 13, 2005 at 08:36:00PM +0100, Darragh wrote:
>>>> Hello, I'm looking for good software TTS. I don't mind paying for it
>>>> at this stage as the apollo sounds horrible in my opinion and when
>>>> using a laptop its not always practicle to plug it in.
>>>>
>>>> I'd like something that I can use on a few applications. At the moment
>>>> I use/try depending on my mood Gnopernicus, Speakup, Yasr, Emacspeak,
>>>> BrlTTY, and in a few weeks the SuSE sbl packages.
>>>>
>>>> So far I've tried Flite, F lite, Festivle and of course the apollo but
>>>> all have sounded terrible or have been very sluggish. I've been told
>>>> about a TTS package from ibm called ttsynth that works with gnopernicus
>>>> and sbl so I'm thinking of buying that but I'd like your input first.
>>>> Does it work with some or all of the above packages and is it
>>>> responsive in the console and in Gnome?
>>>>
>>>> I've had the IBM viavoice package for years but never got it running.
>>>> Today I almost got there however I had problems trying to find
>>>> libXm.so.1 so I think that's going to be left for another very quiet
>>>> day.
>>>>
>>>> Thanks.
>>>>
>>>> Darragh
>>>>
>>>> _______________________________________________
>>>> Speakup mailing list
>>>> Speakup@braille.uwo.ca
>>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>
> --
> This message is subject to the CSIR's copyright, terms and conditions and
> e-mail legal notice. Views expressed herein do not necessarily represent
> the
> views of the CSIR.
>
> CSIR E-mail Legal Notice
> http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html
> CSIR Copyright, Terms and Conditions
> http://mail.csir.co.za/CSIR_Copyright.html
> For electronic copies of the CSIR Copyright, Terms and Conditions and the
> CSIR
> Legal Notice send a blank message with REQUEST LEGAL in the subject line
> to
> HelpDesk@csir.co.za.
>
>
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean. MailScanner thanks Transtec
> Computers for their support.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.344 / Virus Database: 267.10.24/100 - Release Date: 9/13/2005
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Darragh
` Kenny Hitt
` Willem van der Walt
` hank smith [this message]
` Sean McMahon
Darragh
` Willem van der Walt
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='010101c5b943$7bae6020$821a3fce@ron0wrfld8igzk' \
--to=hanksmith4@earthlink.net \
--cc=speakup@braille.uwo.ca \
/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).