public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Willem van der Walt <wvdwalt@csir.co.za>
To: speakup mailing list <speakup@braille.uwo.ca>
Subject: synth_direct usage question
Date: Fri, 2 Jul 2010 10:29:15 +0200 (SAST)	[thread overview]
Message-ID: <Pine.LNX.4.64.1007021018060.17211@localhost.localdomain> (raw)

Good day,
I were under the impression that I can echo a 1 to the synth_direct ebntry 
in the /sys/accessibility/speakup directory to tell speakup to just pass 
the punct/special chars directly to the synthesizer.
When I did that, it spoke the one and I also saw that the "file" has -w- 
-w- -w- permitions, 
, write-only.
This with openttsd and ospeakup running, not that that should be relevant.
I obviously got the use of synth_direct wrong, could someone please 
correct me in how I should go about in doing what I want?
I am working on northern sotho for espeak, a language that has quite a 
number of 
chars above decimal code 128 and I need to get them spoken in speakup.
This can also be terminal settings, but sometimes, I get <C5> when the 
char is dec 197, so its the hex code for the character and not the symbol 
that I here.
Any ideas?
TIA, Willem


-- 
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.


             reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Willem van der Walt [this message]
 ` Gregory Nowak
 ` William Hubbs
   ` Willem van der Walt

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=Pine.LNX.4.64.1007021018060.17211@localhost.localdomain \
    --to=wvdwalt@csir.co.za \
    --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).