From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Character pronounciation
Date: Mon, 2 Mar 2009 15:09:38 -0700 [thread overview]
Message-ID: <20090302220938.GA11580@localhost.localdomain> (raw)
In-Reply-To: <Pine.BSF.4.64.0903021323520.86386@server1.shellworld.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Mar 02, 2009 at 01:52:29PM -0800, Hart Larry wrote:
> An example, yesterday some1 posted the path where
> the characters file could fix the letter zee.
> So I go there-and-with sudo in nano
> I edit that file, make all my changes.
> Once I exit, the file is automaticly set back
> to defaults. Maybe I should do
> a chmod 755 on that directory.
This sounds to me more like user error, rather than inadequate
functionality on the part of speakup or gnu/linux. I'll try to help by
addressing your concerns above one by one. First, you don't want to
open the characters file in a editor like nano. What you want to do is
to make a copy of it, perhaps in your home directory, with cp. Once
you've made a copy of it, open that copy in nano, and do with it what
you need to do. Then, you need to cat your copy to speakup's
characters file with a command similar to this:
cat $HOME/characters >/sys/module/speakup/parameters/characters
Note that speakup's characters file will be back to the defaults when
you reboot, and maybe if you switch synths, (I'm not sure on
that). So, you need to put the above command into a script that runs
at boot. As for your comment about doing chmod 755 on that directory,
/sys/module/speakup/parameters is already at 755 on all of my systems,
and I suspect that this is the norm, and not an exception. If you were
to change permissions on that directory, I also suspect that this
change would also not stick across reboots, unless it was in a script,
but I could be wrong here too. Hth.
Greg
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkmsWSIACgkQ7s9z/XlyUyDtUwCgx9Uqjmz4t+P6EplHH12gf6Un
9bkAoIfg8Hx0ln2yQCOpd6z8CASDsWna
=l5Br
-----END PGP SIGNATURE-----
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline
` Hart Larry
` Gregory Nowak [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=20090302220938.GA11580@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).