DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16268>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16268 ant.apache.org uses tables for formatting. ------- Additional Comments From [EMAIL PROTECTED] 2003-01-20 20:33 ------- I think the XML/XSLT suggestion is not a straw man at all, but rather a good suggestion. Serving XML and XSLT content directly from the site is clearly not the way to go, as relatively few browsers handle this reliably. However, if the site is authored in XML, you can generate content offline in the desired format - HTML with tables, HTML with CSS, XSL-FO for generating PDFs etc. - from the XML sources using a stylesheet processor such as Xalan. You then serve the generated content. This is the way that I now develop websites, and is the reason why I'm interested in Ant: I wanted a build tool to manage the task of transforming my XML-based documents into browser-friendly HTML. On the subject of tables, I recommend staying with them for the time being. Yes, separation of logical and visual structure (which using minimalistic XHTML and CSS would theoretically give you) is the way to go in the long run, but in the short run there are still many users whose browsers won't reliably handle XHTML or CSS-based layout. These people will be locked out of using the Ant site, something which I think is contrary to the spirit of Ant and Apache. I'd recommend going the XML route, but - as I am now in the throes of converting a vast HTML website to XML - I can tell you that it's quite a lot of work. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
