From: "Glenn At Home" <GlennErvin@cableone.net>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: Voxin questions
Date: Sun, 27 Jan 2019 12:27:18 -0600 [thread overview]
Message-ID: <8EB4E80C1BE54D58A091B32CB82E84DA@NUCPPYH> (raw)
In-Reply-To: <0de63897-0b90-e36b-7a37-16df22932079@bluegrasspals.com>
I use it on any and all of my own installations with just the one purchase.
----- Original Message -----
From: "Jayson Smith" <jaybird@bluegrasspals.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Sent: Sunday, January 27, 2019 12:16 PM
Subject: Voxin questions
Hi,
I just installed Debian 9.7 on a new system, and got it talking with
Espeakup. I'm seriously considering the purchase of Voxyn since I cannot
stand Espeak. I have a few questions.
1. Does Voxyn contain any DRM? Please note that I am in no way intending
to do anything illegal, I just want to know what I'm getting into. The
license says it can only be used on one machine, is this enforced? In
other words, if I need to reinstall Linux for any reason, do I need to
do something to free up my license, pray at the temple of the
authorization gods and hope they grant me another license, buy a second
copy of Voxin at full price, or none of these?
2. Is install as simple as it seems? From what I gather, you just buy
Voxyn, download it, unpack it, install it, then install Voxynup, and
you're good to go? Any possible complications to be aware of? This is a
64-bit system by the way.
Thanks,
Jayson
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Jayson Smith
` Glenn At Home [this message]
` Jayson Smith
` Chime Hart
` Chime Hart
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=8EB4E80C1BE54D58A091B32CB82E84DA@NUCPPYH \
--to=glennervin@cableone.net \
--cc=speakup@linux-speakup.org \
/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).