Re: [Chicken-users] Chicken manual in Texinfo format

[Zbigniew]

Not that this solves your problem, but you can do a one-time, one-way
eggdoc->wiki transformation using the eggdoc-svnwiki egg.
(http://chicken.wiki.br/eggdoc-svnwiki, generated using itself :)

But there is no way to retain the semantic information during the conversion.

If some support were added for semantic information in the wiki, I
would be glad to update the conversion egg.  However I would prefer
that some reasonably human readable and writable syntax be used, not
cluttery XML tags.

I've come around to believing the wiki is a good solution for
documentation simply for ease of creation and collaborative updating.
For eggs especially the .info and .pdf output was not very important.
However, I do agree that the Chicken HTML manual is a huge pain, far
more cumbersome than the texinfo version, and the PDF is a step down
from the old one--but that is the tradeoff.

On 6/4/07, address@hidden <address@hidden> wrote:
> On Fri, Jun 01, 2007 at 12:43:28AM +0000, Alejandro Forero Cuervo wrote:
>
> >
> > Can you provide a simplistic example of how an egg would be documented
> > in the wiki using these tags and what the actual html produced would
> > be?
> >
> > Thanks!
> >
>
> Is it possible to have syntax along the lines of the following
> example. Basically, I want to have fixed section names and some code
> that checks that all of the required sections are present in the wiki
> page. Also, it would be nice to have something like the procedure and
> symbol-table formatting elements in eggdoc. And I would prefer that
> the HTML generated out of this is as close to the that produced by
> the eggdoc tool as possible. Or maybe generate sxml that is then parsed
> using the eggdoc stylesheet? Anyway, here is the minimalistic example.