Re: [avrdude-dev] avrdude documentation

[Theodore A. Roth]

On Wed, 26 Feb 2003, Brian Dean wrote:

:) On Wed, Feb 26, 2003 at 01:29:27PM -0800, Sander Pool wrote:
:)
:) > ----- Original Message -----
:) > From: "Joerg Wunsch" <address@hidden>
:) > > > To get LaTeX output to be readable for the on-line PDF, I had to
:) > > > select a non-default font (some kind of Ariel variety), otherwise the
:) > > > result looks chunky and not very good.
:) > >
:) > > \usepackage{times}
:) >
:) > I think the original was in Times but I reported to Brian that his manual
:) > did not look very good with that font. Going to Arial fixed it.
:)
:) Yes, and Sander wasn't the only one - several other folks commented on
:) how difficult the default fonts were to read on-line.  They printed
:) beautifully (at least dvilj4 -> printer did, I never actually printed
:) the resulting PDF), but the on-line PDF looked very poor.
:)
:) I'm going to take a look at latex2html and and see if it is sufficient
:) to do the job.  What would be really nice would be a 'dvi2html', since
:) then it should work no matter how the DVI file was created, whether
:) using LaTeX, or lower level TeX, or whatever.

My experience has been that dvipdf and latex2html generate crappy
output.

Instead of dvipdf, use pdflatex.

Haven't found a good replacement for latex2html.

I think texinfo works better for documentation that latex. Also, I
forgot to mention that autoconf/automake support it out of the box.
Just add a line like this to Makefile.am:

  avrdude_TEXINFOS = avrdude.texi

>From the automake info file:

   In `doc/Makefile.am' we see:

     info_TEXINFOS = hello.texi
     hello_TEXINFOS = gpl.texi

   This is sufficient to build, install, and distribute the GNU Hello
   manual.



Ted