From: "David Poehlman" <poehlman1@home.com>
To: <speakup@braille.uwo.ca>
Subject: Re: Problems with pdf files.
Date: Wed, 16 Jan 2002 16:44:09 -0500 [thread overview]
Message-ID: <00e201c19ed6$eecc2230$c2f20141@cp286066a> (raw)
In-Reply-To: <Pine.LNX.4.33.0201161228140.31983-100000@lnx1.holmesgrown.com>
msaa in linux?
----- Original Message -----
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, January 16, 2002 2:31 PM
Subject: Re: Problems with pdf files.
Optacon? The last one I had cost over $4000! It'll be a cold day in hell
before I could afford something like that. Yes, Optacons fill a unique
nich which just doesn't get filled with current technology. Key here is
getting around copy-protection. I really fault Adobe systems on this
one.
Surely, there's gotta be a way to expose PDF text to the reader with or
with out a password The notion that the MSAA features for the Acrobat
reader are excluded from protected documents is totally stupid and Adobe
should have never come up with this infiror design flaw!!!
On Wed, 16 Jan 2002, David Poehlman wrote:
> there may soon be a new optacon. I hope it will acces directly with a
> pc and also hope that a method of using it with linux is devised.
>
> ----- Original Message -----
> From: "Geoff Shang" <gshang@uq.net.au>
> To: <speakup@braille.uwo.ca>
> Sent: Wednesday, January 16, 2002 10:24 AM
> Subject: Re: Problems with pdf files.
>
>
> On Wed, 16 Jan 2002, Maurice A. Mines wrote:
>
> > is this person a colage student herein the us? if he is he shud be
> asking
> > fore reader services. thats how I get round this problem.
>
> I don't mean to offend anybody, but this is just not good enough. It
> seems
> stupid in this day and age to have to get a sighted person to read you
> something that was produced electronically and I for one wouldn't
stand
> for
> it. It's bad enough that sighted people ask you if you have someone
who
> can see to read it to you, heaven forbid that we have blind people
> advocating the same thing.
>
> OK OK, so if you really need access to something, at least it gets the
> job
> done. but I'd be persuing many other avenues first.
>
> Geoff.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
Thomas Ward
` Kirk Wood
` Thomas Ward
` David Poehlman
` Kirk Wood
` David Poehlman
` Gregory Nowak
` BTBG
` Thomas Ward
` BTBG
` Janina Sajka
` Geoff Shang
` Gregory Nowak
` Steve Holmes
` Maurice A. Mines
` Gregory Nowak
` Maurice A. Mines
` Geoff Shang
` Thomas Ward
` David Poehlman
` Steve Holmes
` David Poehlman [this message]
` Kirk Wood
` Amanda Lee
` Kirk Wood
` Amanda Lee
` Kirk Wood
` Shaun Oliver
` Amanda Lee
` David Poehlman
` Amanda Lee
` David Poehlman
` Thomas Ward
` Amanda Lee
` Thomas Ward
` David Poehlman
` Amanda Lee
` Janina Sajka
` Janina Sajka
` Geoff Shang
` Janina Sajka
` Amanda Lee
` Janina Sajka
` Janina Sajka
` Janina Sajka
` Geoff Shang
` Geoff Shang
` Geoff Shang
` Thomas Ward
` Janina Sajka
` Janina Sajka
` Geoff Shang
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='00e201c19ed6$eecc2230$c2f20141@cp286066a' \
--to=poehlman1@home.com \
--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).