SVG dialect project

SVG is also XHTML. Just a slight correction here. My ML Rebol dialect generates XML, and SVG is a XML dialect, so ML can be used to generate SVG. Andrew Martin ICQ: 26227169 http://Valley.WebPictureBook.com/

Hi, I just want to ask a question about something that I don't understand since a long time now. We have make-doc from RT, we have ML from Andrew, we have make-doc from Chris and finally we have make-doc-pro done by me. This doesn't look like a good product management to me. I might be wrong, but why do we have so many forked projects? What's the benefit of this? I tried to get make-doc-pro to RT nad indicated that I'm willing to tweak to fit their needs. I'm open to new ideas for make-doc-pro, I look forward if others want to jump in and help developing it... One main problem I see in the Rebol community (which I have said several times already) is fragmentation of everything. Docs are fragmented, discussion is fragmented (ML, IOS servers, AltME worlds, you name it), projects with the same goal (or a near-the-same-goal) are fragmented, etc. The success-factor of other open-source projects is that those projects make it to fokus mutually on one goal and share the same vision. This doesn't mean we need to move forward all the same but to spend our energy to find synergy. Petr, please just let's move in small steps and small visions because I know that you see this problem in even more global aspects ;-)). But we didn't made it in the small yet... Anyway, I'm just wondering. Robert

The forking is necessary. RT have not released MD 2.0 source yet. Chris' version removes the irrelevant parts for CGI use, and adds XHTML compliance. He is now looking at adding SVG dialect support instead of the currently supported View dialect. It may be that we have a dialect mechanism to support a number of dialects as plug ins. Your MDP is constrained by your copyright. Andrew's ML is an XML dialect ( I got it wrong before ).

That's life. People have different requirements. But the REP project is an attempt at unification -- to summarise activity on all these discussion groups. Anyway, that's all IMHO -- Graham Chiu http://www.compkarori.com/vanilla Rebol Encyclopaedia Project

I can only explain the motivations behind my own use of Make-Doc, namely the need for minimal and valid XHTML output. I did take care to work within RT's Make-Doc syntax so as to purposely avoid forked development, while adding to the range of output possibilities. I have tried to produce work in a way that will benefit other projects, specifically: http://www.ross-gill.com/r/xhtml-format.r (wip. -- character-level formatting) http://www.ross-gill.com/styles/anywhere.css (style sheet that compliment many of Make-Doc's features) HTH, - Chris