Ayuda con validador html

[rapblack]

1. Error Line 78, Column 134: there is no attribute "src"

…bgcolor" value="#ffffff" /><embed src="proyectoro.swf" quality="high" bgcolor=…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
2. Error Line 78, Column 159: there is no attribute "quality"

…/><embed src="proyectoro.swf" quality="high" bgcolor="#ffffff" width="1200" he…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
3. Error Line 78, Column 174: there is no attribute "bgcolor"

…royectoro.swf" quality="high" bgcolor="#ffffff" width="1200" height="800" name…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
4. Error Line 78, Column 190: there is no attribute "width"

…uality="high" bgcolor="#ffffff" width="1200" height="800" name="proyectoro" al…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
5. Error Line 78, Column 204: there is no attribute "height"

…bgcolor="#ffffff" width="1200" height="800" name="proyectoro" align="middle" a…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
6. Error Line 78, Column 215: there is no attribute "name"

…fffff" width="1200" height="800" name="proyectoro" align="middle" allowScriptA…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
7. Error Line 78, Column 234: there is no attribute "align"

… height="800" name="proyectoro" align="middle" allowScriptAccess="sameDomain" …

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

[rapblack]

8. Error Line 78, Column 261: there is no attribute "allowScriptAccess"

…oro" align="middle" allowScriptAccess="sameDomain" type="application/x-shockwa…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
9. Error Line 78, Column 279: there is no attribute "type"

…" allowScriptAccess="sameDomain" type="application/x-shockwave-flash" pluginsp…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
10. Error Line 78, Column 323: there is no attribute "pluginspage"

…cation/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashpl…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
11. Error Line 78, Column 370: element "embed" undefined

…x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer" />

✉

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 "<frameset>" element),
* by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (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).
12. Error Line 83, Column 94: document type does not allow element "meta" here

…gle-site-verification" content="zrfVKUP0zmD2iI9mHXOnGG058Oo6YpV6UYqnZO0Z1 fw" />

✉

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).
13. Error Line 86, Column 31: document type does not allow element "script" here

<script type="text/javascript">

✉

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).

[JavierB]

Hola rapblack

Muevo tu tema al foro de HTML desde Web general.

Saludos,

[kseso?]

Del traductor de google:
para el error 1

traducción del inglés al español
Ha utilizado el atributo mencionado anteriormente en el documento, pero el tipo de documento que está utilizando no es compatible con ese atributo de este elemento. Este error generalmente es causado por un uso incorrecto del tipo "estricta" del documento con un documento que utiliza marcos (por ejemplo, debe utilizar la "Transición" tipo de documento para obtener el atributo "target"), o mediante el uso de extensiones propietarias como proveedor " marginheight "(esto es por lo general fijado por el uso de CSS para lograr el efecto deseado en su lugar).

Este error también puede producirse si el elemento en sí no es compatible con el tipo de documento que está utilizando, como un elemento definido, no tienen los atributos apoyo, en este caso, el mensaje de error de elemento indefinido para más información.

¿Cómo arreglarlo: comprobar la ortografía y el caso del elemento y atributo, (Recuerde que XHTML es todo en minúsculas) y / o comprobar que ambos son permitidos en el tipo de documento seleccionado, y / o el uso de CSS en lugar de este atributo. Si ha recibido este error cuando se utiliza el elemento <embed> para incorporar medios flash en una página Web, vea el tema Preguntas en flash válida.

Sí, ya sabemos que no es fiable 100%, pero ya le da una pista de por donde van los tiros (usa etiquetas, propiedades, elementos...) no válidos para el tipo de documento (doctype) que declara.

[alexk]

y en cuanto a los errores de html te indica la linea del error asi que tampoco es mucho misterio

[rapblack]

po no lo entiendo

[zerokilled]

no se si te has fijado pero kseso? ha tratado de darte la respuesta, el problema es que el tipo de documento que declaraste aparentemente no es el mismo del cual intentastes validar, o has incluido elementos y atributos que no conforman con el doctype declarado. cuando esto sucede, el validador te señala todos los errores según el doctype que quieres validar. basicamente tienes dos opciones: cambia la declaración del doctype a uno que soporte los atributos/elementos de tu documento; o si estas decidido en un tipo de doctype, tienes que corregir todos los errores indicados. en este caso tienes que leerlos detenidamente para poder entender el porque de los errores. a veces es usas atributos/elementos que no forman parte del doctype o has incluido los elementos en lugares prohibidos.

si tienes paciencia, yo te recomiendo que le dediques tiempo a analizar el documento DTD del cual deseas emplear en tus documentos. no lo prometo, pero vere si luego comparto alguna especie de aplicación que sirva de guía para conecer que elementos o atributos se pueden utilizar según el doctype. tengo una parte realizada pero aún no tengo la idea de como hacerlo un entorno amigable.

[kseso?]

¿me perdí algo? Tres mensajes borrados y 4 votos negativos... ummmh!

po no lo entiendo

¿qué es exactamente lo que no entiende?

[alexk]

Iniciado por kseso?

¿me perdí algo? Tres mensajes borrados y 4 votos negativos... ummmh!

¿qué es exactamente lo que no entiende?

supongo que lo que indica el buscador no entiende ya que no se le ah dicho mas nada