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

Karen Lewellen klewellen at shellworld.net
Wed Feb 22 10:33:27 EST 2023


Josh,
you were the person asking why one could not just, without reasonable 
consent, just declare something is under a public license?
Clearly the person getting permission understands such would be illegal, 
they did not ask the question.



On Wed, 22 Feb 2023, Josh Kennedy wrote:

> It's not up to me to get the permission I forwarded the email but the
> person who needs to get the permission is quite busy this time of year so
> it may take a few months
>
> On Wed, Feb 22, 2023, 00:51 mattias <mjonsson1986 at gmail.com> wrote:
>
>> Seems josh dont realy understand the laws?
>>
>>
>>
>>
>>
>> Skickades från E-post <https://go.microsoft.com/fwlink/?LinkId=550986>
>> för Windows
>>
>>
>>
>> *Från: *Karen Lewellen <klewellen at shellworld.net>
>> *Skickat: *den 22 februari 2023 06:01
>> *Till: *DECtalk <dectalk at bluegrasspals.com>
>> *Ämne: *Re: [DECtalk] Report of a successful use of dectalk with
>> graphical Linux.
>>
>>
>>
>> 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
>>
>


More information about the Dectalk mailing list