public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Problem with accented characters
Date: Sat, 17 Mar 2007 19:42:55 -0700	[thread overview]
Message-ID: <20070318024254.GA17943@localhost.localdomain> (raw)
In-Reply-To: <000301c76903$17930d40$0401a8c0@cleverson>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Mar 17, 2007 at 11:13:54PM -0300, Cleverson wrote:
> I was wondering if chartab may have something to do with this
problem. 

Yes, it does.

> What 
> do mean these codes in chartab, such as "

These are educated guesses, so I do stand to be corrected. I just
figured them out by having a look at the default chartab, since they
do seem to be self-explanatory for the most part. I've placed the
descriptions below the codes.

> B_CTL,
> 

Binary control. These would be characters like ASCII 1-26.

> WDLM,
> 

White-space delimiter. I think the only one that exists is ASCII 32.

> A_PUNC,
> 

Alphabetic punctuation. These would be things like period, exclamation
point, question mark, ETC.

> A_CAP,
> 

Alphabetic capital. In U.S. ASCII these would be 65-90.

> ALPHA,
> 

Probably alphabetic. The opposite of A_CAP. In U.S. ASCII, these would be 97-122.

> B_SYM", etc etc?
> 

Binary symbol. These would be 130-255 in U.S ASCII. They're the
opposite of B_CAP_SYM (probably binary capital symbol), but don't ask
me what the difference between these 2 is. As far as I know, a binary
symbol is just a binary symbol.

Again, these are just educated guesses, so I do stand to be corrected,
but hth somewhat.

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.6 (GNU/Linux)

iD8DBQFF/Kcu7s9z/XlyUyARAq5GAKDF1PBfbz9ptvqOFjJ0qfeq7vlivgCgv0Cx
leSm47dgowFsOJ6djrjtQeI=
=CIM5
-----END PGP SIGNATURE-----


  parent reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Cleverson
 ` Zachary Kline
 ` Gregory Nowak [this message]
   ` almost solved, was " Cleverson
     ` Michael Whapples
 ` Hynek Hanke

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=20070318024254.GA17943@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).