- From: Allan Smith <allan.smith@samsung.com>
- Date: Thu, 26 Feb 2004 14:22:12 +0000
- To: 'Allan Smith' <allan.smith@samsung.com>, www-validator@w3.org
Well actually - having fixed the S it now validates - but still doesn't work Allan -----Original Message----- From: Allan Smith [mailto:allan.smith@samsung.com] Sent: 26 February 2004 14:17 To: 'Allan Smith'; 'www-validator@w3.org' Subject: RE: XHTML validator problems Oops - I do feel a prat - missed the Capital s - Allan -----Original Message----- From: Allan Smith [mailto:allan.smith@samsung.com] Sent: 26 February 2004 14:08 To: 'www-validator@w3.org' Subject: RE: XHTML validator problems I am rewriting an email form - originally in HTML4 transitional Simplified version at http://www.telfordsteamrailway.co.uk/newcss/htmlform.htm I changed the JScript so that in this example validation always fails My XHTML1.1 / CSS verion at http://www.telfordsteamrailway.co.uk/newcss/xhtmlform.html will not verify - it objects to the 'onSubmit" event in the form line did I make a mistake? Or how do I achieve this same process of 'validating' user form entries In XHTML? Allan Smith -----Original Message----- From: Allan Smith [mailto:allan.smith@samsung.com] Sent: 21 January 2004 09:12 To: 'www-validator@w3.org' Subject: XHTML validator problems The page at http://www.telfordsteamrailway.co.uk/testcss.shtml validates as XHTML1.0 Transitional using the online validator at http://validator.w3.org But when I change the DTD to Strict it fails Also if I change the DTD to XHTML 1.1 it fails align="right" not valid in IMG (line 50) But there is no objection to Align="left" in IMG (line58) I'm obviously missing a trick here - help please? If I validate using the online URL (transitional) all is OK But if I use a local copy and upload I get the following error message Note: The HTTP Content-Type header sent by your web browser (unknown) did not contain a "Charest" parameter, but the Content-Type was one of the XML text/* sub-types (text/xml). The relevant specification (RFC 3023) specifies a strong default of "us-ASCII" for such documents so we will use this value regardless of any encoding you may have indicated elsewhere. If you would like to use a different encoding, you should arrange to have your browser send this new encoding information. Any suggestions? Allan Smith Webmanager Telford Steam Railway
Received on Thursday, 26 February 2004 09:22:18 UTC