public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Don Raikes <DON.RAIKES@ORACLE.COM>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: RE: latex:accessible math
Date: Thu, 24 Jan 2013 09:33:20 -0800 (PST)	[thread overview]
Message-ID: <c23b4f64-379a-410f-9db4-552b98299f8f@default> (raw)
In-Reply-To: <kdqvtm$t54$1@ger.gmane.org>

Jason,

What special emacs modes/templates would be useful for working with latex?

-----Original Message-----
From: Jason White [mailto:jason@jasonjgw.net] 
Sent: Thursday, January 24, 2013 2:47 AM
To: speakup@braille.uwo.ca
Subject: Re: latex:accessible math

Scott D. Henning <speakup@linux-speakup.org> wrote:
>The response about LaTex from Liz is right on. I actually use LaTex 
>often for work that might be done in Word, once you get over the first 
>hump to learn it and get some templates built, it is easy to re use 
>them.  Since I am only legally blind, I can tell the output is really 
>good and you are less likely to "break" the document in LaTex than a 
>word processor that takes any keystroke or mouse move as a command.

In 1998 I switched from WordPerfect (a word processor) to LaTeX for all of my writing (aside from Web pages, which are prepared in HTML).

I much prefer LaTeX to a word processor. With LaTeX, I can tell exactly what is in my document simply by reading the source text. The typeset quality is better than that of a word processor, according to publishers and specialists in typography who have used LaTeX for professional purposes. AUCTeX mode in Emacs is a very convenient tool to reduce typing and make entry of the LaTeX commands more convenient. LaTeX is actually a macro system built upon the underlying TeX typesetting tool, and as such, it's programmable.

I wrote my Ph.D. thesis in LaTeX. I wrote law school essays in LaTeX - no mathematics involved in those. My CV is in LaTeX as well. Handouts for university presentations can easily be written in LaTeX. There are classes and packages for these and many other applications.

You can read the generated PDF file with braille or speech output to some extent by converting it to text with the pdftotext tool.

As others have mentioned, there are numerous tutorials and sources of documentation available online. You are welcome to ask me if you would like some references to suitable material.

The only circumstance in which I would use a word processor is a situation requiring collaborative editing of a document with a person who does not use LateX.

Also, if you're preparing documents in LaTeX, you should learn how to use a revision control tool such as Git to track changes to your work. Git is especially good for this, as there is an option that will give you word-by-word diffs rather than line-by-line, and it will even take TeX/LaTeX syntax into account if you specify the right option.


_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

  reply	other threads:[~ UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Littlefield, Tyler
 ` Scott D. Henning
   ` Liz Hare
     ` Littlefield, Tyler
     ` Scott D. Henning
       ` Jason White
         ` Don Raikes [this message]
           ` Liz Hare
           ` Jason White
     ` PS " Scott D. Henning
 ` Kitty Litter
   ` Littlefield, Tyler

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=c23b4f64-379a-410f-9db4-552b98299f8f@default \
    --to=don.raikes@oracle.com \
    --cc=speakup@linux-speakup.org \
    /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).