public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* A Sad day for us in Canada, and who knows elsewhere!
@  Dawes, Stephen
   ` Kirk Wood
   ` Redhat 7.2 and Speakup TALMAGE
  0 siblings, 2 replies; 11+ messages in thread
From: Dawes, Stephen @  UTC (permalink / raw)
  To: Speakup@Braille. Uwo. Ca (E-mail)

I appologize for the off topic posting, but I feel that this is a step
back towards the stone age, and thought others would like to know about
this turn of events.

+_______________________________________________________________________
_______+


Media Release

BC government's decision to withdraw audiobook funding a devastating
decision
for Canadians who are blind: CNIB

January 29 * The Canadian National Institute for the Blind (CNIB) today
expressed its deep regret at the BC government's recent decision to stop
funding the BC Library Services audio book program. 

The reason given for the cut was that commercial audiobooks are now
available
to replace the books recorded in the program. However, the vast majority
of
commercial audiobooks are abridged, and the few that are full-length are
costly. "When it comes to library services, we don't expect sighted
people
to
buy books, or read books that are incomplete," said Jim Sanders,
President
and
CEO of the CNIB. "Why would we expect that of people like myself who are
blind
or visually impaired?"

Only 3-4 per cent of what is published ever makes it into an accessible
format, such as an audio book. With such a huge gap in access to
information,
the loss of any further production in Canada is devastating. The CNIB
Library
and BC Library Services have been sharing titles for 27 years. In 2001,
the
BC
audio book program provided a quarter of the titles added to the CNIB
Library's collection. Many of these titles were Canadian content and not
available anywhere else.

"Even though I live in Alberta, this hurts me and all other
print-disabled
Canadians who want original Canadian content in an accessible format,"
said
CNIB client Gerry Chevalier. "I have read many, many audiobooks over the
years
that were produced by BC Library Services."  

"More than 3 million Canadians cannot read print because of a
disability.
This
decision marks the last exit of a Canadian government from the creation
of
general English-language accessible content. It is regrettable, because
all
other major industrialized nations fund the production of braille and
audio
books for people who are blind or visually impaired," said Sanders.
"Sighted
Canadians have the right to books and information through a local
library.
However, Canadians who are blind do not have that same right."

The $280,000 annual price tag for the audio book program amounted to
only
one
hundredth of one per cent of the total cuts the BC government made on
Jan
21.

Fact Sheet: Access to Information in Canada

When it comes to books, culture, and information for people who need
alternate
formats, there's just not enough out there. The British Columbia
government's
decision to cut its audiobook program is the most recent setback, but
government support in Canada for books for people who are print disabled
has
been eroding now for decades. Here's a look at the numbers behind the
problem...

- Percentage of materials published in Canada that make it into an
alternate
format like an audiobook: 3-4%
  
  - Number of Canadians who need alternate format materials because of a
print
disability (a visual, physical, or learning disability that prevents
them
from
reading print): 3 million, or 10% of the population
  
  - Number of audiobooks Canadian publishers produced in 2000: 814
  
  - Estimated number of these books that were full-length (unabridged):
less
than 5
  
- Typical retail cost of an unabridged audiobook: $50*$200.
  
  - Percentage of new audiobooks (many Canadian content) added to the
CNIB
Library's collection in 2001 that came from BC Library Services: 25% 
  
  - Number of print books available through a local public library
system in
Canada: 1 million and many millions more by inter-library loan
  
  - Number of alternate-format books available in the five wealthiest
countries in the world: 280,000
  
  - Average number of books read by a public library user each year: 1.5
  
  - Average number of books read by a CNIB Library client each year: 60
  
  - Number of the eight major industrialized nations to fund library
services
for people who are blind or visually impaired: 7 (Canada is the only
exception)
  
  - Canadians over age 65 that experience severe vision loss that cannot
be
corrected with standard eyeglasses: 1 in 9
  
  - Canadians over the age of 80: 1 in 4
  
  * 30 *
  
For more information
Julia Morgan
Communications Coordinator
CNIB Library for the Blind
(416) 480-7423


+_______________________________________________________________________
_______+


Steve Dawes
PH:  (403) 268-5527. 
Mailto:  sdawes@gov.calgary.ab.ca 



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: A Sad day for us in Canada, and who knows elsewhere!
   A Sad day for us in Canada, and who knows elsewhere! Dawes, Stephen
@  ` Kirk Wood
     ` Rich Caloggero
   ` Redhat 7.2 and Speakup TALMAGE
  1 sibling, 1 reply; 11+ messages in thread
From: Kirk Wood @  UTC (permalink / raw)
  To: Speakup@Braille. Uwo. Ca (E-mail)

It is truely a sad day. Of course I still wonder why the either or
syndrom? I don't normally listen to books, but have enjoyed listening to a
couple my roomie has (she is blind not me). If the books are read well
then perhaps some of the cost could be recovered by making the same
recording available to sighted people. Not to mention that I know of
several who would listen to more books if they were not often abridged.

I think it is time to call our governments into partnerships. The truth is
that there is a secondary market developing for many of the same
technologies that assist the blind. The most logical thing to me would be
to support development of the technology hoping that it can also find its
way into a secondary market of sighted people. If in partnership the cost
could be recouped to spend on the next thing to be developed.

The same should go for electronic books. I fail to see why there isn't a
huge effort to make the same titles available to the sighted world in the
same basic format.

=======
Kirk Wood
Cpt.Kirk@1tree.net

Nowlan's Theory:
        He who hesitates is not only lost, but several miles from
        the next freeway exit.




^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: A Sad day for us in Canada, and who knows elsewhere!
   ` Kirk Wood
@    ` Rich Caloggero
  0 siblings, 0 replies; 11+ messages in thread
From: Rich Caloggero @  UTC (permalink / raw)
  To: speakup

Making audio books is a very labor intensive process. Think how long it
takes to read a book aloud. Then think about how much time and effort it
takes to do this well. Then think about doing this for one million books
each year (or whatever the number of new books published is per year - some
rediculous number). This quickly becomes unmanagable. However, for many many
people, this is the only way to get such information. In the US, I believe
we have on the order of one to two million audio books all told in our
entire NLS (national library service for the Blind and Physically
Handicapped) system.
To be optomistic, when text to speech technology matures, computers may do
more of this reading. However, I still don't know how emotional content will
be conveyed audibly via TTS. This will require much more semantic analysis
of language, something which simply isn't possible and probably won't be any
time soon. In the next five years, text to speech will probably mature to a
point where inflection will be synthesized to some extent, but reading an
entire book is so much more enjoyable when it is read propperly. Listening
to large amounts of computer generated speech really fatigues me. I don't
see this changing in any real way in the next five years.

Just my opinion...

                    Rich Caloggero

----- Original Message -----
From: "Kirk Wood" <cpt.kirk@1tree.net>
To: "Speakup@Braille. Uwo. Ca (E-mail)" <speakup@braille.uwo.ca>
Sent: 30 January, 2002 5:31 PM
Subject: Re: A Sad day for us in Canada, and who knows elsewhere!


It is truely a sad day. Of course I still wonder why the either or
syndrom? I don't normally listen to books, but have enjoyed listening to a
couple my roomie has (she is blind not me). If the books are read well
then perhaps some of the cost could be recovered by making the same
recording available to sighted people. Not to mention that I know of
several who would listen to more books if they were not often abridged.

I think it is time to call our governments into partnerships. The truth is
that there is a secondary market developing for many of the same
technologies that assist the blind. The most logical thing to me would be
to support development of the technology hoping that it can also find its
way into a secondary market of sighted people. If in partnership the cost
could be recouped to spend on the next thing to be developed.

The same should go for electronic books. I fail to see why there isn't a
huge effort to make the same titles available to the sighted world in the
same basic format.

=======
Kirk Wood
Cpt.Kirk@1tree.net

Nowlan's Theory:
        He who hesitates is not only lost, but several miles from
        the next freeway exit.







^ permalink raw reply	[flat|nested] 11+ messages in thread

* Redhat 7.2 and Speakup
   A Sad day for us in Canada, and who knows elsewhere! Dawes, Stephen
   ` Kirk Wood
@  ` TALMAGE
     ` Janina Sajka
                     ` (3 more replies)
  1 sibling, 4 replies; 11+ messages in thread
From: TALMAGE @  UTC (permalink / raw)
  To: speakup

Hi,

This is probably something simple, but I'm going to ask anyway.
After building about 5 different kernels with Speakup included, and not
getting a boot, I finally figured out that Speakup doesn't like my
LiteTalk.  I switched to a DoubleTalk Lt and got my kernel to boot.  But,
you new a but was coming, the kernel booted fine, no error messages,
Speakup started talking fine, and then when it got to the login prompt, the
speech died.  That's not to say the kernel did, as I can log in from a
terminal fine, but on the local system, no more speech.  One thing I did
notice which may or may not be relevant is, that it said U.S. key map.  I
did check the Speakup key map option when building the kernel though.
Any ideas or suggestions would be appreciated.

Dave Talmage



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Redhat 7.2 and Speakup
   ` Redhat 7.2 and Speakup TALMAGE
@    ` Janina Sajka
       ` Kirk Wood
     ` Dave Hunt
                     ` (2 subsequent siblings)
  3 siblings, 1 reply; 11+ messages in thread
From: Janina Sajka @  UTC (permalink / raw)
  To: speakup

On Wed, 30 Jan 2002 TALMAGE@SOMTEL.COM wrote:

> I finally figured out that Speakup doesn't like my
> LiteTalk.  I switched to a DoubleTalk Lt and got my kernel to boot.

Strange. I don't understand this at all. I use a Litetalk all the time. I 
have one of those expensive ones with both a serial and a parallel port.

> Speakup started talking fine, and then when it got to the login prompt, the
> speech died.

Do Ctrl-Alt-F1 to get a character based login with speakup. You have the 
default runlevel, which is graphical and doesn't talk. Fix this 
permanently by editing /etc/inittab and modifying the line that says:

id:5:initdefault:

You want to change ':5:' to ':3:'

> One thing I did
> notice which may or may not be relevant is, that it said U.S. key map.  I
> did check the Speakup key map option when building the kernel though.

If you have screen review, you're OK. If not, that's the problem, but it 
can be fixed easily enough. Off the top of my head, I don't recall where 
the map lives. So, how about telling us whether or not the above takes 
care of getting into linux with speech. Then, if you don't have screen 
review on the numeric keypad, I can look this up for you--or someone else 
can just jump in before that.




^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Redhat 7.2 and Speakup
     ` Janina Sajka
@      ` Kirk Wood
  0 siblings, 0 replies; 11+ messages in thread
From: Kirk Wood @  UTC (permalink / raw)
  To: speakup

There is another way to change the default run state of a RedHat machine
besides editing the inittab file. If you run setup from the command prompt
there is an option there to deal with this.

=======
Kirk Wood
Cpt.Kirk@1tree.net

Nowlan's Theory:
        He who hesitates is not only lost, but several miles from
        the next freeway exit.





^ permalink raw reply	[flat|nested] 11+ messages in thread

* RE: Redhat 7.2 and Speakup
   ` Redhat 7.2 and Speakup TALMAGE
     ` Janina Sajka
@    ` Dave Hunt
     ` William F. Acker WB2FLW +1-303-777-8123
       [not found]   ` <Pine.LNX.4.44.0201311921540.28645-100000@wb2flw.octothorp. org>
  3 siblings, 0 replies; 11+ messages in thread
From: Dave Hunt @  UTC (permalink / raw)
  To: speakup

Dave,

First of all, the stock RH 7.2 loads the US keymap.  I think you'll find the
line in "/etc/rc.d/rc.local".  Look for a line containing "loadkeys".

Regarding the no speech at login prompt:  I'm guessing you have a "getty"
line in your "/etc/inittab" that puts a login session on the same serial
port as your doubletalk?  If yes, comment it out.  Better yet, make an
"inittab" with and without the line.

Regards,

-Dave



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Redhat 7.2 and Speakup
   ` Redhat 7.2 and Speakup TALMAGE
     ` Janina Sajka
     ` Dave Hunt
@    ` William F. Acker WB2FLW +1-303-777-8123
       [not found]   ` <Pine.LNX.4.44.0201311921540.28645-100000@wb2flw.octothorp. org>
  3 siblings, 0 replies; 11+ messages in thread
From: William F. Acker WB2FLW +1-303-777-8123 @  UTC (permalink / raw)
  To: speakup

Hi,

     Since you mentioned compiling the kernel, I'm going to guess that you 
have an off the shelf version of rh7.2.  If so, from a command prompt, as 
root, do: chkconfig --level 12345 keytable off
That will fix it for the next time you boot.  For the current session, go 
to the drivers/char/speakup directory in your kernel source.  Then do: 
loadkeys speakupmap.map



          HTH.
          Bill in Denver


On Wed, 30 Jan 2002 TALMAGE@SOMTEL.COM wrote:

> Hi,
> 
> This is probably something simple, but I'm going to ask anyway.
> After building about 5 different kernels with Speakup included, and not
> getting a boot, I finally figured out that Speakup doesn't like my
> LiteTalk.  I switched to a DoubleTalk Lt and got my kernel to boot.  But,
> you new a but was coming, the kernel booted fine, no error messages,
> Speakup started talking fine, and then when it got to the login prompt, the
> speech died.  That's not to say the kernel did, as I can log in from a
> terminal fine, but on the local system, no more speech.  One thing I did
> notice which may or may not be relevant is, that it said U.S. key map.  I
> did check the Speakup key map option when building the kernel though.
> Any ideas or suggestions would be appreciated.
> 
> Dave Talmage
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Redhat 7.2 and Speakup
       [not found]   ` <Pine.LNX.4.44.0201311921540.28645-100000@wb2flw.octothorp. org>
@      ` TALMAGE
         ` Janina Sajka
       [not found]       ` <Pine.LNX.4.44.0202010859270.6543-100000@toccata.rednote.ne t>
  0 siblings, 2 replies; 11+ messages in thread
From: TALMAGE @  UTC (permalink / raw)
  To: speakup

Thanks to all who replied to my question.

For those interested in the lessons of the school of hard knocks, and the
problems we can cause ourselves the solution was:
Don't boot your system from a serial terminal and expect speech to work on
the actual linux box.
I was using Grub's serial terminal feature to load and boot my kernel to
test it and that was a bad thing.  I think I'll find when I go back and do
it again, for curiosity sake, I'll find that it wasn't Speakup that was
dead but instead my keyboard.
Thanks especially to Bill who answered the question I didn't even know I
had at the time.  When I finally loaded the kernel from my linux box's
keyboard it was the standard key map that was coming up, and his suggestion
fixed that problem.
As to why my LiteTalk wasn't working, I think it may be to old and
peculiar.  It has a ROM revision of 2.02 and that is the newest it is
capable of taking.  It has an AMD processor and was one of the last ones
MicroTalk put out before changing to an Intel processor.  No biggie though,
I just swapped with the Doubletalk LT I have on my kid's Windows box, and
all works fine now.

Dave Talmage


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Redhat 7.2 and Speakup
       ` TALMAGE
@        ` Janina Sajka
       [not found]       ` <Pine.LNX.4.44.0202010859270.6543-100000@toccata.rednote.ne t>
  1 sibling, 0 replies; 11+ messages in thread
From: Janina Sajka @  UTC (permalink / raw)
  To: speakup

Well, a rom of 2.02 in a Litetalk is pretty old indeed. Mine has been at 
4.77 for about two years now since its last upgrade.

Welcome to speakup and linux, by the way.

On Thu, 31 Jan 2002 TALMAGE@SOMTEL.COM wrote:

> Thanks to all who replied to my question.
> 
> For those interested in the lessons of the school of hard knocks, and the
> problems we can cause ourselves the solution was:
> Don't boot your system from a serial terminal and expect speech to work on
> the actual linux box.
> I was using Grub's serial terminal feature to load and boot my kernel to
> test it and that was a bad thing.  I think I'll find when I go back and do
> it again, for curiosity sake, I'll find that it wasn't Speakup that was
> dead but instead my keyboard.
> Thanks especially to Bill who answered the question I didn't even know I
> had at the time.  When I finally loaded the kernel from my linux box's
> keyboard it was the standard key map that was coming up, and his suggestion
> fixed that problem.
> As to why my LiteTalk wasn't working, I think it may be to old and
> peculiar.  It has a ROM revision of 2.02 and that is the newest it is
> capable of taking.  It has an AMD processor and was one of the last ones
> MicroTalk put out before changing to an Intel processor.  No biggie though,
> I just swapped with the Doubletalk LT I have on my kid's Windows box, and
> all works fine now.
> 
> Dave Talmage
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Redhat 7.2 and Speakup
       [not found]       ` <Pine.LNX.4.44.0202010859270.6543-100000@toccata.rednote.ne t>
@          ` TALMAGE
  0 siblings, 0 replies; 11+ messages in thread
From: TALMAGE @  UTC (permalink / raw)
  To: speakup

Hi Janina,

Thanks for the welcome.
I must admit though, that I'm not totally new to the list as I was a member
2 years ago, and only dropped off when I traded my old Redhat 6.2 box for a
plough truck.  Here in Maine plogh trucks are somewhat important and at the
time I thought I was getting the better end of the deal, but for a while
now I haven't been too sure.  Ever since then I've been intending to put
together another linux box, but until recently I have just been dragging my
feet.  Ten to 15 years ago I was working on a VAX VMS system and after that
a Xenix system, so Linux isn't that big of a transition, just a challenge
for memory retention.
To whoever it was complaining about the Windows header nonsense, I must
apologize as I don't have my modem installed yet on my Linux box as I've
been trying to work out the kimks, and the next thing on my agenda is
getting a CDR installed, and then after that a modem.  I've sort of been
protecting my second serial port for use as a terminal hook up until I'm
satisfied, but as already seen, this can be a burden as well as an asset.

Thanks,
Dave Talmage



^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~ UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 A Sad day for us in Canada, and who knows elsewhere! Dawes, Stephen
 ` Kirk Wood
   ` Rich Caloggero
 ` Redhat 7.2 and Speakup TALMAGE
   ` Janina Sajka
     ` Kirk Wood
   ` Dave Hunt
   ` William F. Acker WB2FLW +1-303-777-8123
     [not found]   ` <Pine.LNX.4.44.0201311921540.28645-100000@wb2flw.octothorp. org>
     ` TALMAGE
       ` Janina Sajka
     [not found]       ` <Pine.LNX.4.44.0202010859270.6543-100000@toccata.rednote.ne t>
         ` TALMAGE

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).