public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: OT: saytime program
Date: Thu, 8 Mar 2007 09:24:35 -0600	[thread overview]
Message-ID: <01cd01c76195$e12afa20$4ba65c90@vv507j> (raw)
In-Reply-To: <20070308015941.GA13012@grml>

I can provide some sound files.  The voice is not the greatest.  Plus, there 
is no "eleven" or "twelve" file, which  would be a problem for a saytime 
program. I got these files off a CD of public domain images and sound files. 
So if you want them, see
http://personalpages.tds.net/~johnheim/sounds/clock/

I don't actually have a saytime program but what I do with these files is 
set up cron jobs to remind me of things. For instance, I have to leave by 
5:10 or I'll miss my bus. So I have a cron job for 5:08 PM that plays 
05.wav, O.wav, and 08.wav.  So at 5:08 PM, my linux box says "five oh 
eight".

Of course, it doesn't work if I'm not in my office. :-)

----- Original Message ----- 
From: "Doug Smith" <bdsmith@oralux.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, March 07, 2007 7:59 PM
Subject: Re: OT: saytime program


> What about this?  Why don't you make your own files.  You can make
> them yourself, or have someone who has a voice you really like, make
> them for you.
>
> All you need to do to make the files is use either the sox rec command
> or arocord, whichever gives you the best results.  When the files are
> made, you can simply do this, and I will be glad to help you find the
> logic to parse the results.
>
> Write a program or some kind of script that can do all of these:
>
> First of all, call the date command.  This can be done in a shell
> command with the exec "date" command or whatever it is, I would have
> to play around for acouple of minutes to find out the exact command
> structure.  This would have to go into a variable which would be
> parsed.
>
> The parsing logic is relatively simple, We can easily see, when we
> use the date command, how many characters are used for each part of
> the results.  So the program would then have to:
>
> look through the string for the first, second, third, etc parts of the
> results of the date command.  Then all we would have to do is this:
>
> decide which files to play.  We can do this by reading what the
> results of our new parsed data variables tell us.  You can have the
> program do all of this, if you want.
>
> If you don't like the standard military time read-outs of date, the
> program can simply subtract 12 from each hour starting at 1300 hours
> or 1:00 PM, and the files could say the time in 12-hour format.
>
> That's all a talking clock, talking digital watch, or any other
> talking time-telling device does.  With all this, use the sox play
> command or the aplay command, each of which will handle mp3 files, and
> you are good to go.  You have your own saytime program.
>
>
>
> Hope this helps.
>
>
>
>
> -- 
> Doug Smith: C.S.F.C.
> Computer Scientist For CHRIST
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> 



  reply	other threads:[~ UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Cheryl Homiak
 ` Doug Smith
   ` John Heim [this message]
  -- strict thread matches above, loose matches on Subject: below --
 Cheryl Homiak
 ` Chuck Hallenbeck
   ` Steve Holmes
     ` Chuck Hallenbeck
 tony seth
 Cheryl Homiak
 Cheryl Homiak
 ` Gene Collins
 ` Lorenzo Taylor
   ` John Heim
     ` Steve Holmes
       ` John Heim
     ` Lorenzo Taylor

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='01cd01c76195$e12afa20$4ba65c90@vv507j' \
    --to=jheim@math.wisc.edu \
    --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).