4 Replies Latest reply: May 10, 2009 3:51 PM by MurraySummers RSS

    After converting a page to xhtml 1.0 Transitional compliant, Dreamweaver indicates a syntax error warning in the head section

    theMikeD Community Member

      I had authored a few pages in HTML4.0 using templates, and all was well.  I decided to convert them to xhtml 1.0 transitional. So I modified the tags to lower case and closed everything and it all validates.

       

      The problem is that in Dreamweaver, it is indicatinga syntac error and I can't figure out why.  The result of this is that the Template path substitution breaks, rendering the generated pages totaly munged.

       

      Here is the head section:

       

      <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
      <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
      <head>
      <!-- TemplateBeginEditable name="head" -->
      <title>TITLE</title>
      <meta name="Description" content="Description of page." />
      <!-- TemplateEndEditable -->
      <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
      <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
      <meta http-equiv="Pragma" content="no-cache" />
      <meta http-equiv="CACHE-CONTROL" content="NO-CACHE" />
      <meta name="robots" content="all follow" />
      <link rel="SHORTCUT ICON" href="favicon.ico" />
      <script src="../common/checkflash.js" language="JavaScript" type="text/JavaScript" />
      <script src="../common/runflash.js" language="JavaScript" type="text/JavaScript" />
      <script src="../common/rollover.js" language="JavaScript" type="text/JavaScript" />
      <script src="../common/weddings.js" language="JavaScript" type="text/JavaScript" />
      <script src="../common/preload-normal.js" language="JavaScript" type="text/JavaScript" />

       

      <link href="../common/weddings.css" rel="stylesheet" type="text/css"  />

       

      And here is the screen showing the error:

       

      Picture 2.JPG

      Is this something simple that I have forgotton? Or is this a bug?

       

      ...Mike