chicken-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] single egg documentation format


From: Ivan Raikov
Subject: Re: [Chicken-hackers] single egg documentation format
Date: Wed, 05 Aug 2009 10:45:40 +0900
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux)

  Alex Shinn has contributed some code to parse wiki content, and I have
modified it to parse svnwiki syntax and placed in the Chicken SVN
repository (in directory release/4/wiki-parse). Peter Bex and I will
work on a suitable replacement for stream-wiki, which will most likely
be an SXML-based system. Others are also welcome to help.

   -Ivan

Ivan Raikov <address@hidden> writes:

>   Ok, I can do some research and see if there is some existing wiki
> parser that can be adapted to read the svnwiki dialect and produce
> s-expressions. If there are some reasonable solutions out there, then I
> will propose an s-expression-based substitute for stream-wiki, and
> some way to automatically merge eggdoc in such a wiki.
>
>    -Ivan
>
> felix winkelmann <address@hidden> writes:
>
>> On Fri, Jul 31, 2009 at 9:02 AM, Ivan Raikov<address@hidden> wrote:
>>
>>> Please do not get rid of eggdoc and seriously consider either finding 
>>> someone
>>> to maintain the wiki software, or using a better source format for the
>>> manual.
>>
>> I doubt that someone will be willing to maintain stream-wiki - it really is
>> rather complex and has loads of dependencies. That wiki2html is a hack
>> is also true, but I'm quite unhappy with the current situation. Having all
>> documentation in a wiki on the other hand is quite convenient and allows
>> more people to help maintain it.
>>
>> Having multiple documentation formats is not acceptable, IMHO, and I
>> hope you agree with that. I personally don't care what format we use,
>> and the easier it is to manipulate in Scheme, the better.
>>
>> So do we need an eggdoc wiki? What are we going to do?




reply via email to

[Prev in Thread] Current Thread [Next in Thread]