On Fri, Jan 05, 2007 at 02:33:24PM +0100, Juergen Auer wrote: > Using Xml/Xsl allows a lot of things without PHP/Perl: The menu (all > filenames, link content, accesskey-definitions) is outsourced into a > single file. Its like a template - without any programming language.
XSL is a programming language, its turing complete at least. Client side XSLT isn't (generally) a great idea though. You do want search engines to be able to read the menu, don't you? Preprocessing solutions work well if you have no server side programming environment available on the server. They also have other advantages, such as making it easier to handle cache control headers. -- David Dorward http://dorward.me.uk ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
