The quick test is to simply change the doctype and hit a validator to see what issues arise from your code and then work through them.
Remember though that if you're changing from XHTML 1.0 Transitional, then you really need to change the way the document is sent to the browser, the mime type really needs to be changed from text/html to application/xhtml+xml. IE won't be able to use this though so you'll need to do something on the server to present an alternative to this (the dominant) browser. See http://xstandard.com/page.asp?p=16A6EBD1-9EEC-4611-98C8-C0F6234B9737 for an explanation and solution (one of many). There are tools that can help you retrofit. I believe HTMLTidy is one of them though I've never used it myself. P > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Neerav > Sent: Sunday, March 21, 2004 8:09 PM > To: WSG > Subject: [WSG] XHTML: 1.0 transitional->1.0 strict->1.1 > > Ive found that coding a new site in XHTML 1.0 transitional is > easy after > some practice, but requires great effort when retrofitting an > old site. > > So now im comfortable using XHTML 1.0 transitional how hard > would moving > to 1.0 strict and then onto 1.1 be? > > I already know that moving to XHTML 1.0 strict leads to problems with > link targets for new pages etc, are there any other > documented problems? > > -- > Neerav Bhatt > http://www.bhatt.id.au > ***************************************************** > The discussion list for http://webstandardsgroup.org/ > See http://webstandardsgroup.org/mail/guidelines.cfm > for some hints on posting to the list & getting help > ***************************************************** > ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************