From: Jason <unleet@qwest.net>
To: speakup@braille.uwo.ca
Subject: Re: ps conversion tools?
Date: Fri, 2 Nov 2001 01:50:45 -0700 [thread overview]
Message-ID: <01110201504502.14000@lightstar> (raw)
In-Reply-To: <15330.21459.377751.980526@bursar.thewatch.net>
> Umm, no, I didn't forget. Yes it needs the x stuff, I think, but it
> works as a command line tool. you just type pdftotext filename and you
> get a text file. Believe me, I'm no more capable of using x than you
> are. I don't actually know where to get it from, but it is a debian
> package.
> I'm sorry I didn't make myself clear earlier.
well, for one, keep in mind most of my comments are intended to be at least a
little bit funny.
and actually in my case, I joined this list to find accessibility-conversion
projects to join (I'm an OK programmer, BTW), and actually I'd like to do
similar work for a living when I'm done with school.
after joining I found out that I can at least answer some of the questions
posted.
my interest in blind-accessiblity issues actually has an interesting (short)
story attached to it, but it's not appropriate for this list, but it includes
an idea I have for accessibility-enhancing DVD-Videos, here's a hint:
mandated DVS won't be very useful without a way to find the menu item that
turns it on ;-)
anyway, I'm way offtopic, so I'll end here.
btw: is there a program like gAIM or everybuddy that runs on a standard
console yet? If not I'd love to hack one together :-)
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
Thomas Ward
` Jason
` Gregory Nowak
` Yvonne Smith
` Jason
` Yvonne Smith
` Jason [this message]
` Shaun Oliver
` tac (was ps conversion tools?) William Hubbs
` ps conversion tools? Buddy Brannan
` Shaun Oliver
` Gregory Nowak
` Yvonne Smith
` Charles Hallenbeck
` Yvonne Smith
` Kirk Reiser
` Janina Sajka
` Steve Holmes
` Janina Sajka
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=01110201504502.14000@lightstar \
--to=unleet@qwest.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).