From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Characters and chartab
Date: Thu, 29 May 2008 19:22:18 -0700 [thread overview]
Message-ID: <20080530022218.GB20774@localhost.localdomain> (raw)
In-Reply-To: <20080530020740.GA6394@babel.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kirk posted on this a bit a while back, and I recall giving an
explanation of both also on this list at some point. Do a search
through the list archives, and hopefully you're run across it. If you
don't find it, I can try to hunt the post down for you from the
archives.
Greg
On Thu, May 29, 2008 at 07:07:40PM -0700, Zachary Kline wrote:
> Hi,
> I was curious as to the purposes of
> /sys/modules/speakup/parameters/chartab and
> /sys/modules/speakup/parameters/characters. They both seem to
> contain character tables of some kind. I was wondering how
> they're populated, and what charset if any they're configured
> for by default? I've noticed some symbols being pronounced,
> such as Greek letters, and was wondering where they come from.
> Any information on this would be appreciated.
> Thanks,
> Zack.
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
- --
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.6 (GNU/Linux)
iD8DBQFIP2Ta7s9z/XlyUyARAsFGAJ4qh6JL2BrnVdpOwytDpo4O8ENdqgCfU1Pg
kgGBxQUUGHZXM5Cl4ikt48s=
=JF9Y
-----END PGP SIGNATURE-----
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline
` 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=20080530022218.GB20774@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).