> From: Peter Donald [mailto:[EMAIL PROTECTED]] > > On Fri, 19 Jul 2002 12:43, Berin Loritsch wrote: > > Now, this may be an abuse of anakia's DTD, > ... > > blah blah blah > > Anakia has no DTD. You can make it do anything you want. You > want academic > purity then go for it, I have more practical requirements, > namely that it > produces web pages...
Hense, the hodgepodge that I don't like. Mixing XHTML and a slightly more semantic XML don't help people who want to contribute. Esp. when some of the docs have one DTD, and others have another. In case you haven't got it yet, I am pushing towards one (1) standard DTD that people besides yourself or I can submit docs for. The fact that there was a standard until new crap came in is not good. If Anakia can do whatever I want (just like Cocoon) then I want it to work with what we have. > You want to put in the work to do it AND MAINTAIN IT OVER > TIME then it will > get done, otherwise it wont. Start small and then work your > way around rather > than hacking up the job till it is halfway there. Anyhows, I > can't see that > happening thou, can you? The mixing of DTDs and lack of standards is not good. As I have said many times before, I don't care what generates the docs. I do care how they look in source and how they look on screen. The Forrest DTDs are a good balance between what Anakia has for its root stuff and what we currently are using. I don't care if you can get the socks in your laundry to create the site from the XML--I don't want the XML forcing our hand on how to represent something. When you mix XHTML and something slightly more formal, that's what you get. So you are fed up with Cocoon, no problem. As long as the docs can get generated regardless of the backend tool it doesn't bother me. I hear your frustration. Things were working until we reorganized Excalibur, and then things went bonkers. It's not a good thing, that's for sure. If I had the time during the transition, I would have been on top of it. Now, I have to make time out of my already incredibly busy schedule. Now, if you want to bring in a tool that does a better job, I am not going to stop you. However, change the tool's stylesheet to make it work with our docs, not the other way around. IT IS NOT MAINTAINABLE TO HAVE TO CHANGE THE DOCS WITH EVERY TOOL. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
