W3C markup validation error.

I've been trying to determine the W3C markup validation error on http://www.kitsapwebdesign.net/business-growth/web-design/index.html The error says "non SGML character number 0 ". Apparently it's some kind of character error, but the error is not visible in the code. Does anyone have any ideas you could suggest to fix it?

Before posting here, I deleted the line 47 on other pages (with the same errors) of the website and it has no effect. Also I may point out any time I save one of the webpages (with or without changing any coding) and re-upload them the errors are gone. But has a warning "Byte-Order Mark found in UTF-8 File".
Your link (of my webpage) passed the validation, but i don't see what you did in the coding to eliminate the errors... it looks identical to the original.
Can you tell me exactly what you did so I can duplicate it so I can fix the other pages on the website?

Similar Messages

Re: W3C Markup Validation Service ??

Am 23.03.2007 schrieb Tantale:
> I used this service
http://validator.w3.org/ to
check my webpage
>
http://www.jmrw.com/Abroad/Barcelone/index.htm
made with Dreamweaver 8.
>
> The result is 206 errors, most of them "end tag omitted,
but OMITTAG NO was
> specified.".
I don't see any errors on your page. It validates fine.
Regards
Inge Grotjahn
CatManiacs World:
http://www.gwsystems.com/inge

Are these errors reported because of some proprietary coding used on the pages that the W3C Page Validator is not equipped to evaluate?
Or, are these reported errors accurate, because the pages get messed up over time because multitudes of folks are constantly making changes, and introducing errors?
It's a little of both. It's also the result of a cost/benefit analysis by the producing bean counters, I think. If the page will display OK without taking the extra time to code properly then why do it? I would also imagine that there is quite a bit of legacy code involved.
The websites to look at are those of the folks who talk the talk....
My personal ethic and workflow prevent me from taking such a cavalier approach.

W3c markup validator?

I submitted a new site that I created (my first) to the w3c validator and got 3 warnings and 1 error:
No Character Encoding Found! Falling back to UTF-8.
Unable to Determine Parse Mode!
No Character encoding declared at document level
Line 1, Column 1: end of document in prolog
The site is www.telluridegravityworks.com.
The source code view shows:
<!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">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
i see charset=utf-8 referenced. Why do I get the validation warning?
The parse model warning seems to be saying that no doc type is declared. I see the doc type in the first line of the code view...?
No character encoding at document level. Is it good practice to declare this twice? Would i just repeat the same tag as above inside of the body tag?
The error about prolog says: >>This error may appear when the validator receives an empty document. Please make sure that the document you are uploading is not empty, and report any discrepancy.<< I don't get this. Should I be concerned or take some action regarding this?
I just typed in the site address like the link above. Should I run each individual page trhough the validator?
Thanks for any help. This is my first site and I want to be sure I haven't made any errors.

Before someone better comes along to answer this I would try including a language declaration like this:
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">

W3C Markup Validation

Can someone please help me understand what it is I need to
fix in order for my site to be W3C compliant?
W3C My site is
my site
Thank you,
Falofal

Falofal posted in macromedia.dreamweaver
> Can someone please help me understand what it is I need
to fix in
> order for my site to be W3C compliant?
http://validator.w3.org/ My
> site is
http://www.sourcelake.ca/test8/
I see you've produced valid XHTML (why XHTML?). You'll also
want to use
their CSS validator at
http://jigsaw.w3.org/css-validator/
Change:
font: "Times New Roman", Times, serif;
to:
font-family: "Times New Roman", Times, serif;
Change:
ssssbackground-color: #333;
to:
background-color: #333;
I don't know what to make of the errors in ul.MenuBarVertical
iframe in
SpryMenuBarVertical.css. They seem to be an IE hack without
actually
targeting IE in the CSS. You might be able to ignore them.
Mark A. Boyd
Keep-On-Learnin' :)

W3C CSS and Markup Validation Service

I just finished my first CSS Web site using PhotoShop, Fireworks, Flash and Dreamweaver. I did the site from the ground up, the visual way according to some tutorials I found that are uploaded at the Adobe Media Player server. The site checks out with zero errors using the CSS and Markup W3C Validation Services. The design holds together at http://browsershots.org/ in 75+ different browsers.
Just for fun, I checked out Adobe's, Apple's, Maximum PC's and Tom's Hardware Guide's homepages using W3C's Validation Services. All of these sites had between 80 and 339 errors per page tested.
Question:
Are these errors reported because of some proprietary coding used on the pages that the W3C Page Validator is not equipped to evaluate?
Or, are these reported errors accurate, because the pages get messed up over time because multitudes of folks are constantly making changes, and introducing errors?

Are these errors reported because of some proprietary coding used on the pages that the W3C Page Validator is not equipped to evaluate?
Or, are these reported errors accurate, because the pages get messed up over time because multitudes of folks are constantly making changes, and introducing errors?
It's a little of both. It's also the result of a cost/benefit analysis by the producing bean counters, I think. If the page will display OK without taking the extra time to code properly then why do it? I would also imagine that there is quite a bit of legacy code involved.
The websites to look at are those of the folks who talk the talk....
My personal ethic and workflow prevent me from taking such a cavalier approach.

Onload error in markup validator

Hi,
Not very good with code.
I have this on load error in markup validator http://validator.w3.org/check?uri=http%3A%2F%2Fwww.denotestationery.com%2Fdenote_localroot %2Fgallery.html&charset=%28detect+automatically%29&doctype=Inline&group=0
In reference to this webpage. It's coming from the Nav bar.
http://www.denotestationery.com/denote_localroot/gallery.html
My question is.... If I delete onload="" code, will it cause me any problems? (I have actually tried this on one of the nav bar images and checked on the browser, and it seems to be ok, although I have not uploaded this recent change to the remote server)

My question is.... If I delete onload="" code, will it cause me any problems? (I have actually tried this on one of the nav bar images and checked on the browser, and it seems to be ok, although I have not uploaded this recent change to the remote server)
I removed the onload event from each of those navbar items (they all have one - not just the one picked up by the validator) and the validator didn't throw an error... actually not even sure why the onload event is writen there as it is actually empty'...
If you remove the onload event, just test in all browsers and if it works, leave it out.
The option to try is to create the navbar on a new blank page and see if it write the code exactly the same - in case there was an error the first time it was done.
Just some suggested troubleshooting ideas - I never use that method to create a navbar and don't have time to even test creating one :-)

W3C Validator Errors

Hi all,
I'm going through my website code and trying to fix any validation errors that are being flagged. See the following:
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.whsfirstaidkits.com.au%2F&charset=%28de tect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.3+http%3A%2F%2Fv alidator.w3.org%2Fservices
It is for the website http://www.whsfirstaidkits.com.au
The 4 errors relate to the shopping cart summary module that I have within my code. I am using the following: <div class="shopping-cart">{module_shoppingcartsummary,horizontal}</div> and BC converts that to: <div class="shopping-cart"><span id="catCartSummary" quote="False" vertical="False"><table cellspacing="0" class="cartSummaryTable"><tr><td class="cartSummaryItem">Shopping cart is empty.</td></tr></table></span></div>
Now the validator says that it is producing the following errors:
Attribute quote not allowed on element span at this point.
Attribute vertical not allowed on element span at this point.
Element table not allowed as child of element span in this context. (Suppressing further errors from this subtree.)
The cellspacing attribute on the table element is obsolete. Use CSS instead.
Since BC generates this code automatically, is there a way to fix this?
Cheers,
Jordan

Same Here!
I have the same issue on a site I'm currently doing W3C checks for.
I tried changing document type to HTML5 from XHTML Transitional, but W3C checks failed on the same things regarding the .{module_shoppingcartsummary}
For comparison, I tested the Appliance King template for a page with the same shopping cart summary;
http://appliance-king-preview.businesscatalyst.com/lcd-tv
It too found the same W3C errors.

1 hard validation error left and I will be w3c validated. Its a tr ending problem. Very hard!

Just recently i started to validate the script for html 4.01 strict and ran into a hard coding problem..
On the home.html
A line of code says
</td>
{if ($smarty.foreach.videos.index+1)%$cols==0}</tr><tr>{/if}
{/foreach}
</tr></table>
<br>
{$pagination}
This code throws a validation error on line 645 which says this
Line 645, Column 7: end tag for "TR" which is not finished
Line 642 through 645 say this on html source when grabbing the source code from my website
</table>
</td>
</tr><tr>
</tr></table>
I think that the problem may be that its blank between a <tr> and </tr>, but i am not sure how to fix this or if this is even the problem. The coding above generates the </tr><tr> and it's generated an extra one for no reason.

I solved it.
I realized that, because it was generating <tr> and then trying to close </tr> </table> I had to place <td> </td> in between them. A simple fix yet it took me a while to figure that out lol. I guess you can easily overlook something like this easily when you didn't write all of it.
Mark

Validation error while creating Web Service Proxy.

Hi,
I'm trying to create Web Service Proxy. But I'm stuck with a Validation error
model error: type
+"{http://xmlns.oracle.com/2001/XMLSchema/DOM}+
+org.w3c.dom.Document" not found.+
I'm using "Create Web Service Proxy" wizard. There are 6 steps in creating proxy through JDev. wizard.
First step itself displaying the above validation error when I click on "Next" button.
Few points
We have created web service using "oracle.j2ee.ws.StatelessJavaRpcWebService" servlet
Thanks in advance.
-Sukumar

Hi,
It might be that the .net service which you have is not WS-I compliant. Can you first run WS-I Analyzer on the wsdl to see it the test passes.
Thanks,
Vishal

Lax validation errors on schema import ('version' exceeds maximum length)

I have a schema as per below. I'm trying to import it into Oracle 10.2.0.2.0. However, I'm getting the following lax validation error:
Error loading ora_business_rule.xsd:ORA-30951: Element or attribute at Xpath /schema[@version] exceeds maximum length
I can fix it by modifying the attribute and shortening it but I'd like to know why it's occuring. Insofar as I can tell there is no imposed limit on the size of schema attributes according to the W3C standard. Which then makes me wonder: does Oracle impose limits on the length of all attributes or is this specific to 'version' ? If there is a limit, what is the upper bound (in bytes) ? Where is this documented?
Cheers,
Daniel
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:br="http://foo.com/BusinessRule_PSG_V001" targetNamespace="http://foo.com/BusinessRule_PSG_V001" elementFormDefault="qualified" attributeFormDefault="unqualified" version="last committed on $LastChangedDate: 2006-05-19 11:00:52 +1000 (Fri, 19 May 2006) $">
     <xs:element name="edit">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="edit_id" type="xs:string"/>
                    <xs:element ref="br:business_rule"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="derivation">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="derivation_id" type="xs:string"/>
                    <xs:element ref="br:derivation_type"/>
                    <xs:element ref="br:business_rule"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="derivation_type">
          <xs:simpleType>
               <xs:restriction base="xs:NMTOKENS">
                    <xs:enumeration value="complex"/>
                    <xs:enumeration value="format"/>
                    <xs:enumeration value="formula"/>
                    <xs:enumeration value="recode"/>
                    <xs:enumeration value="SAS code"/>
                    <xs:enumeration value="transfer"/>
                    <xs:enumeration value="count"/>
                    <xs:enumeration value="sum"/>
                    <xs:enumeration value="max"/>
                    <xs:enumeration value="min"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="business_rule"></xs:element>
</xs:schema>

Opps -- Sorry it's a decision we took when looking at Version
When we registered the Schema for Schemas during XDB bootstrap the Version attriubte was mapped to varchar2(12).
SQL> desc xdb.xdb$schema_T
Name                                      Null?    Type
SCHEMA_URL                                         VARCHAR2(700)
TARGET_NAMESPACE                                   VARCHAR2(2000)
VERSION                                            VARCHAR2(12)
NUM_PROPS                                          NUMBER(38)
FINAL_DEFAULT                                      XDB.XDB$DERIVATIONCHOICE
BLOCK_DEFAULT                                      XDB.XDB$DERIVATIONCHOICE
ELEMENT_FORM_DFLT                                  XDB.XDB$FORMCHOICE
ATTRIBUTE_FORM_DFLT                                XDB.XDB$FORMCHOICE
ELEMENTS                                           XDB.XDB$XMLTYPE_REF_LIST_T
SIMPLE_TYPE                                        XDB.XDB$XMLTYPE_REF_LIST_T
COMPLEX_TYPES                                      XDB.XDB$XMLTYPE_REF_LIST_T
ATTRIBUTES                                         XDB.XDB$XMLTYPE_REF_LIST_T
IMPORTS                                            XDB.XDB$IMPORT_LIST_T
INCLUDES                                           XDB.XDB$INCLUDE_LIST_T
FLAGS                                              RAW(4)
SYS_XDBPD$                                         XDB.XDB$RAW_LIST_T
ANNOTATIONS                                        XDB.XDB$ANNOTATION_LIST_T
MAP_TO_NCHAR                                       RAW(1)
MAP_TO_LOB                                         RAW(1)
GROUPS                                             XDB.XDB$XMLTYPE_REF_LIST_T
ATTRGROUPS                                         XDB.XDB$XMLTYPE_REF_LIST_T
ID                                                 VARCHAR2(256)
VARRAY_AS_TAB                                      RAW(1)
SCHEMA_OWNER                                       VARCHAR2(30)
NOTATIONS                                          XDB.XDB$NOTATION_LIST_T
LANG                                               VARCHAR2(4000)
SQL>

Validating error with JAXP

i wrote a small app that read a COLLADA instance document and convert it to a html document. First I wrote some xsl stylesheets and now I'm using a JAXP DOM parser to parse the instance document and a JAXP xslt transformer to perform the transformation.
When I use a non-validating parser it seems all work well but when i try to use a validating parser i get this message error:
org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'xml:base' to a(n) 'attribute declaration' component.
What does it mean?
When I'm at my home pc,I get the error above but when I'm at university lab pc I don't get any error. WHY!? I'm using the same files.
Thx for your help

i'm using jdk 1.5.0_11 and here is my java code.
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.FactoryConfigurationError;
import javax.xml.parsers.ParserConfigurationException;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.w3c.dom.Document;
import org.w3c.dom.DOMException;
// For JFileChooser
import javax.swing.*;
// For write operation
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
import java.io.*;
public class StylizerMio2 {
    // Global value so it can be ref'd by the tree-adapter
    static Document document;
    // Constants you'll use when configuring the factory
    static final String JAXP_SCHEMA_LANGUAGE="http://java.sun.com/xml/jaxp/properties/schemaLanguage";
    static final String W3C_XML_SCHEMA="http://www.w3.org/2001/XMLSchema";
     //Constants used to specify the schema in the application
     static final String schemaSource="COLLADASchema_141.xsd";
     static final String JAXP_SCHEMA_SOURCE="http://java.sun.com/xml/jaxp/properties/schemaSource";
    public static void main(String[] argv) {
        /*if (argv.length != 2) {
            System.err.println("Usage: java StylizerMio stylesheet xmlfile");
            System.exit(1);
        // Generating a parser
        DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
         //Configure the factory to generate a namespace-aware,validating parser
        factory.setValidating(true);
        factory.setNamespaceAware(true);
         try{
              factory.setAttribute(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
          // Associate a document with a schema
          factory.setAttribute(JAXP_SCHEMA_SOURCE, new File(schemaSource));
         catch (IllegalArgumentException x) {
              // Happens if the parser does not support JAXP 1.2
              x.printStackTrace();
        // Associating the document with the schema
        try {
          JFileChooser chooser = new JFileChooser();
        ExampleFileFilter daeFilter = new ExampleFileFilter();
        daeFilter.addExtension("dae");
        daeFilter.setDescription("documenti istanza COLLADA");
        chooser.setFileFilter(daeFilter);
        chooser.setCurrentDirectory(new File("."));
          int returnVal = chooser.showOpenDialog(null);
          if(returnVal == JFileChooser.APPROVE_OPTION) {
          System.out.println("You chose to open this file: " +
               chooser.getSelectedFile().getName());
            File stylesheet = new File("trasformazione.xsl");
          //"Moon Buggy/lunar_vehicle_tris.dae"
            File datafile = chooser.getSelectedFile();
            DocumentBuilder builder = factory.newDocumentBuilder();
          //Handling validation errors
          builder.setErrorHandler(
          new org.xml.sax.ErrorHandler(){
               // ignore fatal errors (an exception is garaunteed)
               public void fatalError(SAXParseException exception)
                    throws SAXException{}
                         //treat validation errors as fatal
                         public void error(SAXParseException e)
                              throws SAXParseException
                              throw e;
                         // dump warnigs too
                         public void warning(SAXParseException err)
                              throws SAXParseException
                              System.out.println("** Warning"
                              + ", line " + err.getLineNumber()
                              + ", uri " + err.getSystemId());
                              System.out.println("   " + err.getMessage());
            document = builder.parse(datafile);
            // Use a Transformer for output
            TransformerFactory tFactory = TransformerFactory.newInstance();
            StreamSource stylesource = new StreamSource(stylesheet);
            Transformer transformer = tFactory.newTransformer(stylesource);
            DOMSource source = new DOMSource(document);
            // SaveDialogue JFileChooser
            ExampleFileFilter htmlFilter = new ExampleFileFilter();
            htmlFilter.addExtension("html");
            htmlFilter.setDescription("documento html");
            chooser.setFileFilter(htmlFilter);
             chooser.showSaveDialog(null);
              //"Moon Buggy/lunar_vehicle_tris.html"
            File htmlFile= chooser.getSelectedFile();
            StreamResult result = new StreamResult(htmlFile);
            transformer.transform(source, result);
        } catch (TransformerConfigurationException tce) {
            // Error generated by the parser
            System.out.println("\n** Transformer Factory error");
            System.out.println("   " + tce.getMessage());
            // Use the contained exception, if any
            Throwable x = tce;
            if (tce.getException() != null) {
                x = tce.getException();
            x.printStackTrace();
        } catch (TransformerException te) {
            // Error generated by the parser
            System.out.println("\n** Transformation error");
            System.out.println("   " + te.getMessage());
            // Use the contained exception, if any
            Throwable x = te;
            if (te.getException() != null) {
                x = te.getException();
            x.printStackTrace();
        } catch (SAXException sxe) {
            // Error generated by this application
            // (or a parser-initialization error)
            Exception x = sxe;
            if (sxe.getException() != null) {
                x = sxe.getException();
            x.printStackTrace();
        } catch (ParserConfigurationException pce) {
            // Parser with specified options can't be built
            pce.printStackTrace();
        } catch (IOException ioe) {
            // I/O error
            ioe.printStackTrace();
    } // main
}

W3C CSS validator says it can't find my spry folder

I'm trying to put the finishing touches on my first site, but when I sent it through the W3C CSS validator it failed. The error message is:
File not found: http://www.smallfarming101.com/../SpryAssets/SpryMenuBarHorizontal.css: Bad Request File not found:
The Spry Assets folder is there in the public_html folder and just to be sure, I deleted the existing folder and ftp'd an updated one. Why is the validator not happY? Thanks.
http://www.smallfarming101.com

Hi,
the only thing I can imagine why W3 reports an error is this: ".. /" in your http://www.smallfarming101.com/../SpryAssets/SpryMenuBarHorizontal.css. Presumably, it is not necessary. This depends how deep your spry files are nested.
Hans-G.

W3c html validation problem

hello,
I´m developing my website and wanted him to be mobile compatible, but i got into a w3c validation error wich I´m not finding a solution.
for mobile devices, and as far as I´ve searched over the net, it is comum practice to use
<ul id="testing" selected="true">
<li id="li1">something here</li>
</ul>
the problem is w3c says ul can´t have selected as propertie, so what I wanted to ask is what can I do to make this work in comum browsers and in mobile devices?
this selected="true is needed to make javascript work, so it is a kind of variable wich is used in a if statment.
Thanks, look to read from you soon
Pluda

Thanks, I´m going to try your sample.
the goal is making noe interface who works everywhere, I tryed this on sony ericson and iphone, on mozila firefox, google chrome, safari and internet explorer (in ie it doesn´t work)
the navigation is like an iphone app, you have one list of topics, and when you click on one of them, all the content moves from right to left, revealing the correspondent list content.
Nancy O. told me I should validate in w3c, and I did, I get no errors if I remove the selected="true", but then no movement happens and nothing is revealed.
The javascript is simple, is a for in loop trought the list items, checking if selected is true or not. if true, it moves elements, otherwise it doesn´t.
I just don´t see an inteligent way of replacing the selected=true for other thing.
the example is the same you already saw in my previous post, http://www.mataborrao.com/teste the js file is in http://www.mataborrao.com/teste/js/navegacao.js

ASP Javascript Validation Error -

Help!!!!
Hi, i would appreciate some help on the following validation
error i get the error is -
"The tag: "script" doesn't have an attribute: "runat" in
currently active versions.[XHTML 1.0 transitional]" - where the
code that i have used is -
"<script language="vbscript" runat="server">
function PreserveWhitespace(str)
tabStr =
chr(160)&chr(160)&chr(160)&chr(160)&chr(160)
str = Replace(str,chr(10),chr(10)&"<BR>")
str = Replace(str,chr(9),tabStr)
PreserveWhitespace = str
End Function
</script>"
I've used this code to ensure that the data returned from the
database is correctly formatted - however the validation error is
causing the site not to be w3c validated -
Appreciate the help --

.NET does not support VBScript. If your not using .NET, get
rid of the runat="server"

Validation errors - html4.0 errors

hi folks
when i validate (dwv cs3) I get validation errors (about 50 of them) such as
The tag: "td" doesn't have an attribute: "background" in currently active versions.[HTML 4.0]
or
tag: " p" invalid inside tag: "p". " p" closing tag is optional. Validation will proceed as if context is closed.[HTML 4.0]
or
The tag: "meta" has an XML style closing syntax for an empty element even though version: "HTML20" is not an XML tag language.[HTML 4.0]
I have no idea why I am getting these -
any help much appreciated!

jadopt1999 wrote:
hi folks
when i validate (dwv cs3) I get validation errors (about 50 of them) such as
The tag: "td" doesn't have an attribute: "background" in currently active versions.[HTML 4.0]
This one for example is telling you that you cannot declare a background image inside the html for the table cell. You need to define a background via a stylesheet.
You are probably using a XHTML 1.0 Transitional or Strict Doctype in the head of the document which means that you cannot use deprecated html attributes.
If you can't fix the errors due to your not understanding the error messages, you can convert the page to a less strict doctype by going to File>Convert>HTML 4.01 Transitional - this is a little more lenient in what is allowed.
You can then upload your files to a server and test the validation with the W3C validation tool: This at least tells you how to possibly fix the problems you encounter,.
HTML Validator - http://validator.w3.org
CSS Validator - http://jigsaw.w3.org/css-validator/
Or if you use Firefox, you can do this on your local files using the Web Developer Toolbar.
If you still have problems, then post a link to your pages, so others can take a look and offer suggestions :-)

W3C markup validation error.

Similar Messages

Maybe you are looking for