[DECtalk] Report of a successful use of dectalk with graphical Linux.

joshknnd1982 at gmail.com joshknnd1982 at gmail.com
Wed Feb 22 17:48:36 EST 2023


So do you need this official statement by a former fonix employee to be in
writing? As a recording? Or both? Let me know. I thought of a former
employee who I can get in touch with. 


-----Original Message-----
From: Dectalk <dectalk-bounces at bluegrasspals.com> On Behalf Of Karen
Lewellen
Sent: Wednesday, February 22, 2023 17:40
To: DECtalk <dectalk at bluegrasspals.com>
Subject: Re: [DECtalk] Report of a successful use of dectalk with graphical
Linux.

Again, given what the public license says about requirements, you would 
need   such an agreement not to care in writing.  because that license 
agreement says otherwise.



On Wed, 22 Feb 2023, joshknnd1982 at gmail.com wrote:

> A downpayment for decTalk. for compiling it for android.
>
>
> -----Original Message-----
> From: Dectalk <dectalk-bounces at bluegrasspals.com> On Behalf Of Karen 
> Lewellen
> Sent: Wednesday, February 22, 2023 14:44
> To: DECtalk <dectalk at bluegrasspals.com>
> Subject: Re: [DECtalk] Report of a successful use of dectalk with 
> graphical Linux.
>
> Actually, not really.
> And again, you have this refusal documented in what way?
> Hearsay is not legally binding.
> If the parties involved are so willing to sign away their rights, they 
> can legally sign away their rights.
> And a down payment for what exactly?
>
>
>
> On Wed, 22 Feb 2023, joshknnd1982 at gmail.com wrote:
>
>> I offered to pay them $1000 as a downpayment. That is quite a 
>> substantial amount don't you think?
>> And they said no.
>>
>>
>> -----Original Message-----
>> From: Dectalk <dectalk-bounces at bluegrasspals.com> On Behalf Of Karen 
>> Lewellen
>> Sent: Wednesday, February 22, 2023 11:13
>> To: DECtalk <dectalk at bluegrasspals.com>
>> Subject: Re: [DECtalk] Report of a successful use of dectalk with
> graphical
>> Linux.
>>
>> And just what motivation are you providing for them to care?
>>
>>
>>
>> On Wed, 22 Feb 2023, Josh Kennedy wrote:
>>
>>> Yes I reached out to code Factory they are not the same company they 
>>> do not care at all.
>>>
>>> On Wed, Feb 22, 2023, 10:58 Karen Lewellen 
>>> <klewellen at shellworld.net>
>> wrote:
>>>
>>>> And  you have likewise reached out to code factory?
>>>> It is possible they may be the same company?
>>>> Nothing personal, but given your question about how public licenses 
>>>> work, can we be assured that those you have contacted will take 
>>>> this matter seriously?
>>>>
>>>>
>>>>
>>>> On Wed, 22 Feb 2023, joshknnd1982 at gmail.com wrote:
>>>>
>>>>> No sorry. Jake is quite busy this time of year so I reached out to 
>>>>> others who may know the fonix employees who gave the code to us. 
>>>>> If there is any progress I'll let you know.
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Dectalk <dectalk-bounces at bluegrasspals.com> On Behalf Of 
>>>>> Karen Lewellen
>>>>> Sent: Wednesday, February 22, 2023 10:00
>>>>> To: DECtalk <dectalk at bluegrasspals.com>
>>>>> Subject: Re: [DECtalk] Report of a successful use of dectalk with
>>>> graphical
>>>>> Linux.
>>>>>
>>>>> And, it is not likely to join android until the legal barriers are
>>>> removed.
>>>>> Any progress on that front?
>>>>>
>>>>>
>>>>>
>>>>> On Wed, 22 Feb 2023, Josh Kennedy wrote:
>>>>>
>>>>>> Too bad it doesn't run on Android yet. Well at least we have 
>>>>>> espeak with all of its new variants such as Glenn and wave and 
>>>>>> many others
>> now.
>>>>>>
>>>>>> On Wed, Feb 22, 2023, 00:01 Karen Lewellen 
>>>>>> <klewellen at shellworld.net>
>>>>> wrote:
>>>>>>
>>>>>>> because that requires permission.
>>>>>>> why not get that permission from the individuals providing the 
>>>>>>> source code?
>>>>>>> Anyone adding a general public license must have the right to do 
>>>>>>> as
>>>> much.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, 21 Feb 2023, Josh Kennedy wrote:
>>>>>>>
>>>>>>>> Well why not just go on to its GitHub page and remove all the 
>>>>>>>> licenses
>>>>>>> and
>>>>>>>> just replace them with the general public license?
>>>>>>>>
>>>>>>>> On Tue, Feb 21, 2023, 23:17 Karen Lewellen 
>>>>>>>> <klewellen at shellworld.net>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi members,
>>>>>>>>> Sharing this post from the blind Linux users group.  Hope it
>>>> generates
>>>>> a
>>>>>>>>> smile.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------- Forwarded message ----------
>>>>>>>>> Date: Tue, 21 Feb 2023 22:59:35 -0500
>>>>>>>>> From: Linux for blind general discussion 
>>>>>>>>> <blinux-list at redhat.com>
>>>>>>>>> To: Linux for blind general discussion 
>>>>>>>>> <blinux-list at redhat.com>
>>>>>>>>> Subject: What a find! DECTalk!
>>>>>>>>>
>>>>>>>>> I'm happy to be in the fediverse right now. Looking through my
>>>>>>> timeline, I
>>>>>>>>> just
>>>>>>>>> found a link to a Github repository that has DECTalk source 
>>>>>>>>> code, apparently released by some of the original DECTalk 
>>>>>>>>> developers.
>>>>>>>>>
>>>>>>>>> https://github.com/dectalk/dectalk
>>>>>>>>>
>>>>>>>>> The LICENSE file still has scary words like "proprietary" and 
>>>>>>>>> "confidential"
>>>>>>>>> and "all rights reserved," but the source builds and works. I 
>>>>>>>>> have it working in speech-dispatcher with Orca as I write this.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Note that this is the DECTalk software version 4.x, the one 
>>>>>>>>> that
>>>> sounds
>>>>>>>>> just
>>>>>>>>> like the DECTalk Express from the 1990's, so anyone who needs
>>>> hardware
>>>>>>>>> speech
>>>>>>>>> should feel right at home with this. No, this is not the 5.x 
>>>>>>>>> DECTalk
>>>>>>> that
>>>>>>>>> really sounds like crap. Have fun and enjoy, and I do hope 
>>>>>>>>> they fix
>>>>> this
>>>>>>>>> license soon. It would be good to have another truly free 
>>>>>>>>> speech synthesizer to play with, and this is definitely a huge 
>>>>>>>>> step in that direction.
>>>>>>>>>
>>>>>>>>> ~ Kyle
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Blinux-list mailing list
>>>>>>>>> Blinux-list at redhat.com
>>>>>>>>> https://listman.redhat.com/mailman/listinfo/blinux-list
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Dectalk mailing list
>>>>>>>>> Dectalk at bluegrasspals.com
>>>>>>>>> https://bluegrasspals.com/mailman/listinfo/dectalk
>>>>>>>>>
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Dectalk mailing list
>>>>>>> Dectalk at bluegrasspals.com
>>>>>>> https://bluegrasspals.com/mailman/listinfo/dectalk
>>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> Dectalk mailing list
>>>>> Dectalk at bluegrasspals.com
>>>>> https://bluegrasspals.com/mailman/listinfo/dectalk
>>>>>
>>>>> _______________________________________________
>>>>> Dectalk mailing list
>>>>> Dectalk at bluegrasspals.com
>>>>> https://bluegrasspals.com/mailman/listinfo/dectalk
>>>>>
>>>> _______________________________________________
>>>> Dectalk mailing list
>>>> Dectalk at bluegrasspals.com
>>>> https://bluegrasspals.com/mailman/listinfo/dectalk
>>>>
>>>
>> _______________________________________________
>> Dectalk mailing list
>> Dectalk at bluegrasspals.com
>> https://bluegrasspals.com/mailman/listinfo/dectalk
>>
>> _______________________________________________
>> Dectalk mailing list
>> Dectalk at bluegrasspals.com
>> https://bluegrasspals.com/mailman/listinfo/dectalk
>>
> _______________________________________________
> Dectalk mailing list
> Dectalk at bluegrasspals.com
> https://bluegrasspals.com/mailman/listinfo/dectalk
>
> _______________________________________________
> Dectalk mailing list
> Dectalk at bluegrasspals.com
> https://bluegrasspals.com/mailman/listinfo/dectalk
>
_______________________________________________
Dectalk mailing list
Dectalk at bluegrasspals.com
https://bluegrasspals.com/mailman/listinfo/dectalk



More information about the Dectalk mailing list