Important Warnings The validator has found the following problem(s) prior to validation, which should be addressed in priority: Character Encoding mismatch! The character encoding specified in the HTTP header (iso-8859-15) is different from the value in the element (iso-8859-1). I will use the value from the HTTP header (iso-8859-15) for this validation. ↑ Top Validation Output: 43 Errors Line 24, Column 7: element "CENTER" undefined. ✉ You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by: incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "" element), by using vendor proprietary extensions such as "" or "" (this is usually fixed by using CSS to achieve the desired effect instead). by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case). Line 25, Column 4: end tag for "br" omitted, but OMITTAG NO was specified.
✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". Line 25, Column 0: start tag was here.
Line 26, Column 4: end tag for "br" omitted, but OMITTAG NO was specified.
✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". Line 26, Column 0: start tag was here.
Line 28, Column 193: document type does not allow element "object" here. …b#version=8" width="600" height="248">\n');✉ The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed). One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error). Line 29, Column 118: cannot generate system identifier for general entity "slogan1". …als/blubberintro1.swf?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+enco✉ An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs". Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters. If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem. Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed. Line 29, Column 118: general entity "slogan1" not defined and no default entity. …als/blubberintro1.swf?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+enco✉ This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. Line 29, Column 125: reference not terminated by REFC delimiter. …bberintro1.swf?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("✉ If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. Line 29, Column 125: reference to external entity in attribute value. …bberintro1.swf?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("✉ This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'. Line 29, Column 125: reference to entity "slogan1" for which no system identifier could be generated. …bberintro1.swf?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("✉ This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. Line 29, Column 117: entity was defined here. …bals/blubberintro1.swf?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+enc Line 29, Column 139: an attribute specification must start with a name or name token. …?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("")+'&urlTo='+e✉ An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name). Line 29, Column 140: end tag for "param" omitted, but OMITTAG NO was specified. …color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("")+'&urlTo='+en✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". Line 29, Column 22: start tag was here. document.write('\n');✉ If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. Line 31, Column 33: there is no attribute "src". document.write(' element to incorporate flash media in a Web page, see the FAQ item on valid flash. Line 31, Column 110: reference not terminated by REFC delimiter. …bberintro1.swf?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("✉ If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. Line 31, Column 110: reference to external entity in attribute value. …bberintro1.swf?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("✉ This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'. Line 31, Column 110: reference to entity "slogan1" for which no system identifier could be generated. …bberintro1.swf?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("✉ This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. Line 29, Column 117: entity was defined here. …bals/blubberintro1.swf?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+enc Line 31, Column 124: an attribute specification must start with a name or name token. …?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("")+'&urlTo='+e✉ An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name). Line 31, Column 124: element "embed" undefined. …?color=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("")+'&urlTo='+e✉ You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by: incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "" element), by using vendor proprietary extensions such as "" or "" (this is usually fixed by using CSS to achieve the desired effect instead). by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case). Line 31, Column 136: reference not terminated by REFC delimiter. …FFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("")+'&urlTo='+encodeURI("ht✉ If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. Line 31, Column 136: reference to entity "slogan2" for which no system identifier could be generated. …FFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("")+'&urlTo='+encodeURI("ht✉ This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. Line 29, Column 143: entity was defined here. …or=0xFFFFFF&slogan1='+encodeURI("")+'&slogan2='+encodeURI("")+'&urlTo='+encod Line 31, Column 160: reference not terminated by REFC delimiter. …"")+'&slogan2='+encodeURI("")+'&urlTo='+encodeURI("http://abdullahdogan.tr.gg✉ If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. Line 31, Column 160: reference to entity "urlTo" for which no system identifier could be generated. …"")+'&slogan2='+encodeURI("")+'&urlTo='+encodeURI("http://abdullahdogan.tr.gg✉ This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. Line 29, Column 169: entity was defined here. …deURI("")+'&slogan2='+encodeURI("")+'&urlTo='+encodeURI("http://abdullahdogan Line 31, Column 222: reference not terminated by REFC delimiter. …llahdogan.tr.gg?seenintro=1")+'&image='+encodeURI("http://")+'" quality="high✉ If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. Line 36, Column 28: value of attribute "method" cannot be "POST"; must be one of "get", "post".

✉ The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed. Line 37, Column 77: end tag for "input" omitted, but OMITTAG NO was specified. …nt-size:px;background-color:;" value="">✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". Line 37, Column 0: start tag was here. Line 38, Column 48: end tag for "input" omitted, but OMITTAG NO was specified. ✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". Line 38, Column 0: start tag was here. Line 29, Column > 80: XML Parsing Error: EntityRef: expecting ';'. …alue="https://img.webme.com/designs/globals/blubberintro1.swf?color=0xFFFFFF&sl…✉ Line 29, Column > 80: XML Parsing Error: attributes construct error. …alue="https://img.webme.com/designs/globals/blubberintro1.swf?color=0xFFFFFF&sl…✉ Line 29, Column > 80: XML Parsing Error: Couldn't find end of Start Tag param line 29. …alue="https://img.webme.com/designs/globals/blubberintro1.swf?color=0xFFFFFF&sl…✉ Line 29, Column > 80: XML Parsing Error: EntityRef: expecting ';'. …alue="https://img.webme.com/designs/globals/blubberintro1.swf?color=0xFFFFFF&sl…✉ Line 29, Column > 80: XML Parsing Error: EntityRef: expecting ';'. …alue="https://img.webme.com/designs/globals/blubberintro1.swf?color=0xFFFFFF&sl…✉ Line 29, Column > 80: XML Parsing Error: EntityRef: expecting ';'. …alue="https://img.webme.com/designs/globals/blubberintro1.swf?color=0xFFFFFF&sl…✉ Line 31, Column > 80: XML Parsing Error: EntityRef: expecting ';'. ….198.45.22/designs/globals/blubberintro1.swf?color=0xFFFFFF&slogan1='+encodeU…✉ Line 31, Column > 80: XML Parsing Error: attributes construct error. ….198.45.22/designs/globals/blubberintro1.swf?color=0xFFFFFF&slogan1='+encodeU…✉ Line 31, Column > 80: XML Parsing Error: Couldn't find end of Start Tag embed line 31. ….198.45.22/designs/globals/blubberintro1.swf?color=0xFFFFFF&slogan1='+encodeU…✉ Line 31, Column > 80: XML Parsing Error: EntityRef: expecting ';'. ….198.45.22/designs/globals/blubberintro1.swf?color=0xFFFFFF&slogan1='+encodeU…✉ Line 31, Column > 80: XML Parsing Error: EntityRef: expecting ';'. ….198.45.22/designs/globals/blubberintro1.swf?color=0xFFFFFF&slogan1='+encodeU…✉ Line 31, Column > 80: XML Parsing Error: EntityRef: expecting ';'. ….198.45.22/designs/globals/blubberintro1.swf?color=0xFFFFFF&slogan1='+encodeU…✉ Line 32, Column 32: XML Parsing Error: Opening and ending tag mismatch: object line 28 and embed. document.write('\n');✉ Line 33, Column 30: XML Parsing Error: Opening and ending tag mismatch: script line 27 and object. document.write('\n'); ✉ Line 34, Column 9: XML Parsing Error: Opening and ending tag mismatch: br line 26 and script. ✉ Line 39, Column 7: XML Parsing Error: Opening and ending tag mismatch: input line 38 and form.

✉ Line 41, Column 9: XML Parsing Error: Opening and ending tag mismatch: input line 37 and CENTER. ✉ Line 43, Column 7: XML Parsing Error: Opening and ending tag mismatch: form line 36 and body. ✉ Line 44, Column 7: XML Parsing Error: Opening and ending tag mismatch: br line 25 and html. ✉ Line 44, Column 7: XML Parsing Error: Premature end of data in tag CENTER line 24. ✉ Line 44, Column 7: XML Parsing Error: Premature end of data in tag body line 23. ✉ Line 44, Column 7: XML Parsing Error: Premature end of data in tag html line 2. ✉