Re: [avrdude-dev] Documentation build tools requirements - many complaints

[E. Weddington]

Joerg Wunsch wrote:

> As E. Weddington wrote:
>
>  
>
> > Another option, that I'm exploring for both a "WinAVR user manual"
> > and for avr-libc, is the use of AsciiDoc (google for it). It's a
> > text file, with very minimal formatting that gets translated by the
> > "asciidoc" program, a Python script, and it can output HTML and
> > Docbook (as well as LinuxDoc).
> >    
>
> I'm a bit sceptical of Yet Another Doc Converter, as doxygen has shown
> us (in avr-libc) that we often enough ended up with wanting more than
> the automatic conversion could provide for us.  I'm currently more
> inclined to use docbook directly for avr-libc.  
I understand.

So far, my only objection with using DocBook directly is just trying 
find a decent editor (in Windows) that can handle the format. The format 
is pretty verbose if you have to write it raw.

My only limitation that I currently have is figuring out how to convert 
DocBook to PDF. Cygwin doesn't seem to have a quick and easy solution 
out of the box. The "xmlto" that comes with Cygwin can convert DocBook 
to FO (among other things), but it stops there. No direct to PDF.

If anyone knows of a solution to this I would be most grateful.

My only other reasoning for AsciiDoc is that what it provides is "good 
enough", at least for the WinAVR user manual.

> As Eric Raymond's tool
> could save all the existing man page work for avrdude into docbook
> format, it seems to be an option to me here, too.
>  
Which tool is this?

Eric