public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Glenn at home" <GlennErvin@cableone.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Online Documentation
Date: Wed, 28 Jun 2006 18:19:08 -0500	[thread overview]
Message-ID: <013e01c69b09$424273a0$6a00a8c0@desktop> (raw)
In-Reply-To: <Pine.LNX.4.62.0606211054410.1199@buyshish.verizon.net>

I would like html, if it was all on one page, but I hate that constant 
linking to new pages while I am into reading something.
So if this is impossible, I would prefer txt over HTML, as it would be all 
in one page/document.

Glenn
----- Original Message ----- 
From: "Dan Murphy" <danmint@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, June 21, 2006 9:55 AM
Subject: Re: Online Documentation


Actually I think html is my most preferred format since if it's done
well, one can navigate quickly and efficiently arounbd in the document.
On
Thu, 15 Jun 2006, Steve Holmes wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> t curious.
>
> What format do you all like your online electronic documentation in?  I
> mean as choices plain text, HTML, postscript, PDF, info (compiled from
> teXinfo), man pages, etc.
>
> I'm asking this partly because I'm fixin' to build some Slackware based
> packages for Exim and others and have a choice as to what kind of
> documentation to include.  In particular, Exim has I think four
> different formats available for their documentation and would be added
> separately when installed.  I really don't wanna bloat the package with
> four different formats so hence my question.  I'm personally torn
> between HTML and info.  The HTML versions are easiest to include where
> info, you have to be careful with the global dir file.
>
> Anyway, I just thought I'd ask to get other people's ideas on this
> subject.  I have a Slackware compatible package for Exim 4.62 ready to
> go as soon as I work out the manual preference.  I could actually leave
> it as is with their plain text format and let the end user fetch the
> other formats on their own.  I will also have Slack packages for Speech
> Dispatcher and Speechd-up available shortly.
>
> - --
> HolmesGrown Solutions
> The best solutions for the best price!
> http://ld.net/?holmesgrown
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.7 (GNU/Linux)
>
> iD8DBQFEkZG9WSjv55S0LfERA/gpAKDdiIxg8BiwOPq3VUJ754y+WMkCIwCg0Aj7
> 9/JWfFv3EDh2TpkAI1coXTw=
> =an2F
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

so long as the people do not care to exercise their freedom, those
who wish to tyrannize will do so; for tyrants are active and ardent,
and will devote themselves in the name of any number of gods, religious
and otherwise, to put shackles upon sleeping men.
                 -- Voltarine de Cleyre.

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup 



  reply	other threads:[~ UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Steve Holmes
 ` Charles Hallenbeck
 ` Alex Snow
 ` Eunice
   ` Steve Holmes
     ` Charles Hallenbeck
 ` Gregory Nowak
   ` Tyler Littlefield
 ` Ralph W. Reid
 ` Dan Murphy
   ` Glenn at home [this message]
     ` David Poehlman
       ` Steve Holmes
         ` David Poehlman
 online documentation Jude DaShiell
 ` Tyler Littlefield

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='013e01c69b09$424273a0$6a00a8c0@desktop' \
    --to=glennervin@cableone.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).