public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: why PDF
Date: Mon, 14 Jan 2002 13:30:31 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0201141321460.7867-100000@lbear> (raw)
In-Reply-To: <007001c19d2c$7e6143f0$4c015112@vantaa>

Rich recently speculated on why some things become standards. It boils
down to formating. The reason PDF has become popular is that it is the
only means which a publisher can eb sure their layout remains intact. A
PDF doc will look the same regardless of the computer and/or printer
used. There could be a breakdown in print resolution, but a 8.5 by 11 page
will have the line breaks the same regardless of the medium.

The argument is of course that the information is more important then the
formatting. But when someone spends a butt load of time and effort on
formatting to help convey information they aren't keen on throwing it
out. Further, it is much harder to make formatting that adjusts well to
all resolutions. If you don't understand this, leave it to "one of the
stupid sited things."

Then of course there is conversion factors. MIT can convert much of its
course work to PDF much cheaper then HTML. Figure much is probably already
in Word format. Add in a program and you can convert this to PDF in
minutes. To do a good job of HTML will take much longer if there is any
advanced formatting. Manpower is more expensive then licensing in many
cases. Especially when they can negotiate the later. Adobe will give a
huge break in fees to MIT if all courses are published in their
format. This way they can stick it to others at a better (for them) price
later. This is also why m$ charges a university less then half of retail
for their products.

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

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




  reply	other threads:[~ UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 anti-word Rich Caloggero
 ` Kirk Wood [this message]
   ` why PDF Janina Sajka
 ` (off-topic) ADA Geoff Shang
   ` Janina Sajka
     ` Kirk Wood
       ` David Poehlman
         ` Maurice A. Mines
           ` Kenny Hitt
             ` Kirk Wood
               ` Kenny Hitt
                 ` David Poehlman
                   ` Amanda Lee
                     ` (off-topic) Reader Services Kirk Wood
                       ` Amanda Lee
                         ` David Poehlman
                           ` Amanda Lee
                             ` David Poehlman
                               ` Amanda Lee
                         ` Kirk Wood
                     ` (off-topic) ADA Kenny Hitt
       ` Janina Sajka
         ` Geoff Shang
           ` Janina Sajka
         ` Amanda Lee
           ` Janina Sajka
             ` Amanda Lee
         ` Amanda Lee
   ` Angelo Sonnesso

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=Pine.LNX.4.21.0201141321460.7867-100000@lbear \
    --to=cpt.kirk@1tree.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).