From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Problems with pdf files.
Date: Tue, 15 Jan 2002 07:30:41 -0500 [thread overview]
Message-ID: <009b01c19dc0$72bc28a0$0100a8c0@tward> (raw)
In-Reply-To: <019f01c19d3d$74b3f080$9489160c@michweb.net>
That's the problem. They insist pdf documents are accessible because of
Adobe's 5.0 release. However, what they aren't getting is I am trying to
read a document on Linux, and Adobe for Linux doesn't work with speech.
It is a case were I am going to have to call them back, and insist on
talking to some high level official, and tell them the problem.
Perhaps tell them if they don't cooperate with my accessible needs I may
have to get a lawyer, and see if they are violating some accessability laws.
After all they insist it is accessible, but only accessible to those with
new Microsoft based technologies.
----- Original Message -----
From: BTBG <kheltsley@shell.core.com>
To: <speakup@braille.uwo.ca>
Sent: Monday, January 14, 2002 3:52 PM
Subject: Re: Problems with pdf files.
> Would it be possible to contact the publisher of the PDF to get a password
> to unlock the encryption? I assume that that would be Sam's?
>
> from
> Keith H.
>
>
>
> --- You Wrote: ---
>
> > when I inquired about it Sam's said they did that for copy protection.
Is
> > there anyway to force a pdf file into text when it has been secured?
> >
> > I'm getting frustrated because although Sam's will give me ebooks they
> > insist on pdf format only.
> >
> >
> >
> > _______________________________________________
> > 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 [this message]
` 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
` 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='009b01c19dc0$72bc28a0$0100a8c0@tward' \
--to=tward@bright.net \
--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).