Re: another round for configuration.txt => html

2011-11-03 Thread Aleksandar Lazic
Hi, On 03.11.2011 06:40, Baptiste wrote: because writting the tool to do it is more fun and easier to maintain than a whole doc to parse again after each patch. :) I'm not sure if I understand you right. What I have understand is that you write a tool which make a ascii2markdown translation,

Re: another round for configuration.txt => html

2011-11-02 Thread Baptiste
because writting the tool to do it is more fun and easier to maintain than a whole doc to parse again after each patch. :) On Thu, Nov 3, 2011 at 6:23 AM, carlo flores wrote: > Just curious: why not rewrite the docs in markdown? > > Would a rewrite formulinix could just add to be welcome? > > On

Re: another round for configuration.txt => html

2011-11-02 Thread carlo flores
Just curious: why not rewrite the docs in markdown? Would a rewrite formulinix could just add to be welcome? On Wednesday, November 2, 2011, Baptiste wrote: > Hi Aleks, > > It's a good and interesting start. > I already talked to Willy about the doc format, and unfortunately for > you, the way y

Re: another round for configuration.txt => html

2011-11-02 Thread Baptiste
Hi Aleks, It's a good and interesting start. I already talked to Willy about the doc format, and unfortunately for you, the way you're doing is not the one wanted by him. As you have remarked, the doc format is quite "open", each documentation contributors tries to maintain the format, but there

another round for configuration.txt => html

2011-11-02 Thread Aleksandar Lazic
Hi all, I have now started do change the configuration.txt in that way that asciidoc an produce nice HTML output. asciidoc -b html5 -o haproxy-conf.html configuration.txt http://www.none.at/haproxy-conf.html I have stopped at section 2.3 to get your feedback. As you can see in the diff there