>Agreed :) I'll try and help out too. XHTML is very >interesting, that's for >sure. >Maybe we could go with Strict: there is almost only CSS used >in this site, >although I'm not sure if XHTML allows things like align="right", etc.
Well Strict is just that - Strict (very). You can use aligns, if they are provided by CSS or within an embedded "style" tag. Like our sites policy, XHTML (Strict) is all about seperating content from presentation. Our site is mostly CSS driven, and the conversion should be relatively simple (even for strict). However, "Transitional" allows us to use tags that Strict won't - which I think is massively important for backward compatibility (ie: those browsers that don't support CSS). The main rules of XHTML are: 1) Every tag must have closure (eg: </tag> or <... /> (which is used for tags that don't normally have closure, like <br>, <img>, <hr>, <meta>, etc.) 2) Lower case must be used for all tags and attributes (names, not values) 3) The "name" tag is deprecated - "id" should be used as its counterpart 4) The "DOCTYPE" must be defined 5) The "charset" must be defined 6) The document must be "well-formed" The XHTML references are all available at http://www.w3c.org/ (naturally). In converting Shapeshifter, I have found the process to be very easy. But Shapeshifter was already based on well-formed code. Jonathan M. Hollin - WYPUG Co-ordinator West Yorkshire Perl User Group http://wypug.pm.org/ http://wypug.digital-word.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
