Ouin le html 4 je suis intéressé...mais
33 messages
• Page 1 sur 3 • 1, 2, 3
Consultez la formation au REFERENCEMENT naturel Google de WebRankInfo / Ranking Metrics
- jeanguy
- WRInaute discret
- Messages: 160
- Inscription: 25 Juil 2004
Ouin le html 4 je suis intéressé...mais
le Mer Aoû 04, 2004 14:42
Est ce que vous avez des liens pour que je puisse convertire mon site de html à celui de 4????????
J'ai fait un teste de validation, et il est écris que :
I was not able to extract a character encoding labeling from any of the valid sources for such information. Without encoding information it is impossible to reliably validate the document. I'm falling back to the "UTF-8" encoding and will attempt to perform the validation, but this is likely to fail for all non-trivial documents.
So what should I do? Tell me more...
Sorry, I am unable to validate this document because on lines 84, 98, 118 it contained one or more bytes that I cannot interpret as utf-8 (in other words, the bytes found are not valid values in the specified Character Encoding). Please check both the content of the file and the character encoding indication.
Je ne comprend pas hihihihihihi.......
En tout cas, j'ai besoin d'aide car je vais enlever mes frames et reconstruire en html 4
Je suis débutant quand même
J'ai fait un teste de validation, et il est écris que :
I was not able to extract a character encoding labeling from any of the valid sources for such information. Without encoding information it is impossible to reliably validate the document. I'm falling back to the "UTF-8" encoding and will attempt to perform the validation, but this is likely to fail for all non-trivial documents.
So what should I do? Tell me more...
Sorry, I am unable to validate this document because on lines 84, 98, 118 it contained one or more bytes that I cannot interpret as utf-8 (in other words, the bytes found are not valid values in the specified Character Encoding). Please check both the content of the file and the character encoding indication.
Je ne comprend pas hihihihihihi.......
En tout cas, j'ai besoin d'aide car je vais enlever mes frames et reconstruire en html 4
Je suis débutant quand même
-
Bool - WRInaute passionné
- Messages: 1290
- Inscription: 26 Fév 2004
le Mer Aoû 04, 2004 14:58
euh.... je suppose que ton site est déjà en HTML 4, mais en "HTML 4 Craditional" 
Tu peux toujours jeter un oeil ici : http://openweb.eu.org/xhtml/ Sachant que le HTML 4.01 Strict est presque identique au XHTML 1.0 Strict
Tu peux toujours jeter un oeil ici : http://openweb.eu.org/xhtml/ Sachant que le HTML 4.01 Strict est presque identique au XHTML 1.0 Strict
-
thickparasite - WRInaute passionné
- Messages: 1289
- Inscription: 26 Avr 2003
le Mer Aoû 04, 2004 16:34
Est-ce que c'est ton site sur le profil ? Si oui, c'est Lycos qui te met le bazar avec leur code horrible.
Si non, il s'agit d'une ligne de ton HEAD manquante qu'il signifie l'encodage.
Ca ressemble à ça :
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
Si non, il s'agit d'une ligne de ton HEAD manquante qu'il signifie l'encodage.
Ca ressemble à ça :
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-
Monique - WRInaute passionné
- Messages: 1545
- Inscription: 16 Sep 2002
le Mer Aoû 04, 2004 16:38
Bonjour,
Sans doute n'as-tu pas spécifié l'encodage des caractères choisi :
Si tu as choisi le HTML 4.01 strict, c'est
Amicalement,
Monique
Sans doute n'as-tu pas spécifié l'encodage des caractères choisi :
- Code: Tout sélectionner
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html lang="fr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Titre de la page</title>
</head>
Si tu as choisi le HTML 4.01 strict, c'est
- Code: Tout sélectionner
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
Amicalement,
Monique
Dernière édition par Monique le Mer Aoû 04, 2004 16:42, édité 1 fois.
- jeanguy
- WRInaute discret
- Messages: 160
- Inscription: 25 Juil 2004
Monique à l'aide avec ton code et pour les pros
le Mer Aoû 04, 2004 16:53
voici ce que ça donne avec ton code :
No DOCTYPE Found! Falling Back to HTML 4.01 TransitionalA DOCTYPE Declaration is mandatory for most current markup languages and without one it is impossible to reliably validate this document. I am falling back to "HTML 4.01 Transitional" and will attempt to validate the document anyway, but this is very likely to produce spurious error messages for most non-trivial documents.
So what should I do? Tell me more...
DOCTYPE Fallback in effect!
The DOCTYPE Declaration in your document was not recognized. This probably means that the Formal Public Identifier contains a spelling error, or that the Declaration is not using correct syntax. Validation has been performed using a default "fallback" Document Type Definition that closely resembles HTML 4.01 Transitional, but the document will not be Valid until you have corrected the problem with the DOCTYPE Declaration.
This page is not Valid HTML 4.01 Transitional!
Below are the results of attempting to parse this document with an SGML parser.
Line 4, column 0: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
<HTML>
The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with the HTML 4.01 Transitional DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.
✉
Line 8, column 29: required attribute "TYPE" not specified
<script language="javascript">
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
✉
Line 64, column 111: end tag for element "TITLE" which is not open
...r ception, produit du terroir.</TITLE>'+
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occured in a script section of your document, you should probably read this FAQ entry.
✉
Line 65, column 9: end tag for "SCRIPT" omitted, but its declaration does not permit this
'</HEAD><frameset rows="62,*" frameborder="0" border="0" framespacing="0" onlo
✉
Line 8, column 0: start tag was here
<script language="javascript">
Line 65, column 9: end tag for "HEAD" which is not finished
'</HEAD><frameset rows="62,*" frameborder="0" border="0" framespacing="0" onlo
Most likely, You nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element (e.g. 'ul') which requires a child element (e.g. 'li') that you did not include. Hence the parent element is "not finished", not complete.
✉
Line 65, column 25: there is no attribute "ROWS"
'</HEAD><frameset rows="62,*" frameborder="0" border="0" framespacing="0" onlo
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.
✉
Line 65, column 44: there is no attribute "FRAMEBORDER"
...AD><frameset rows="62,*" frameborder="0" border="0" framespacing="0" onload="
✉
Line 65, column 55: there is no attribute "BORDER"
...t rows="62,*" frameborder="0" border="0" framespacing="0" onload="setLoad()"
✉
Line 65, column 72: there is no attribute "FRAMESPACING"
...meborder="0" border="0" framespacing="0" onload="setLoad()" onunload="stopMov
✉
Line 65, column 83: there is no attribute "ONLOAD"
..." border="0" framespacing="0" onload="setLoad()" onunload="stopMove()">'+
✉
Line 65, column 104: there is no attribute "ONUNLOAD"
...cing="0" onload="setLoad()" onunload="stopMove()">'+
✉
Line 65, column 116: element "FRAMESET" undefined
...oad="setLoad()" onunload="stopMove()">'+
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), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
✉
Line 66, column 14: there is no attribute "SRC"
'<FRAME src="http://iquebec.ifrance.com/heberg/pub.htm?Time=1091634013&Nom=let
✉
Line 66, column 73: cannot generate system identifier for general entity "Nom"
...e.com/heberg/pub.htm?Time=1091634013&Nom=leterroirdelestrie&FRAME=1" name="pu
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.
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 66, column 73: general entity "Nom" not defined and no default entity
...e.com/heberg/pub.htm?Time=1091634013&Nom=leterroirdelestrie&FRAME=1" name="pu
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 66, column 76: reference to entity "Nom" for which no system identifier could be generated
...om/heberg/pub.htm?Time=1091634013&Nom=leterroirdelestrie&FRAME=1" name="pubfr
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 66, column 72: entity was defined here
...ce.com/heberg/pub.htm?Time=1091634013&Nom=leterroirdelestrie&FRAME=1" name="p
Line 66, column 96: cannot generate system identifier for general entity "FRAME"
...me=1091634013&Nom=leterroirdelestrie&FRAME=1" name="pubframe" scrolling="no"
✉
Line 66, column 96: general entity "FRAME" not defined and no default entity
...me=1091634013&Nom=leterroirdelestrie&FRAME=1" name="pubframe" scrolling="no"
✉
Line 66, column 101: reference to entity "FRAME" for which no system identifier could be generated
...91634013&Nom=leterroirdelestrie&FRAME=1" name="pubframe" scrolling="no" nores
✉
Line 66, column 95: entity was defined here
...ime=1091634013&Nom=leterroirdelestrie&FRAME=1" name="pubframe" scrolling="no"
Line 66, column 110: there is no attribute "NAME"
...Nom=leterroirdelestrie&FRAME=1" name="pubframe" scrolling="no" noresize frame
✉
Line 66, column 131: there is no attribute "SCROLLING"
...e&FRAME=1" name="pubframe" scrolling="no" noresize frameborder="0" border="0"
✉
Line 66, column 145: "NORESIZE" is not a member of a group specified for any attribute
...e="pubframe" scrolling="no" noresize frameborder="0" border="0" framespacing=
✉
Line 66, column 157: there is no attribute "FRAMEBORDER"
... scrolling="no" noresize frameborder="0" border="0" framespacing="0">'+
✉
Line 66, column 168: there is no attribute "BORDER"
..."no" noresize frameborder="0" border="0" framespacing="0">'+
✉
Line 66, column 185: there is no attribute "FRAMESPACING"
...meborder="0" border="0" framespacing="0">'+
✉
Line 66, column 188: element "FRAME" undefined
...order="0" border="0" framespacing="0">'+
✉
Line 67, column 95: element "FRAME" undefined
...order="0" border="0" framespacing="0">'+
✉
Line 76, column 8: end tag for element "SCRIPT" which is not open
</script>
✉
Line 81, column 2: "DOCTYPE" declaration not allowed in instance
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
✉
Line 83, column 15: document type does not allow element "HTML" here
<html lang="fr">
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 91, column 50: "NORESIZE" is not a member of a group specified for any attribute
<frame name="entete.html"src="pages.html"noresize scrolling="yes">
✉
Line 91, column 65: element "FRAME" undefined
...entete.html"src="pages.html"noresize scrolling="yes">
✉
Line 93, column 68: element "FRAMESET" undefined
...*"frameborder="yes"border="50%" framespacing="1%">
✉
Line 94, column 33: "NORESIZE" is not a member of a group specified for any attribute
<frame src="Entete.html"noresize scrolling="no">
✉
Line 94, column 47: element "FRAME" undefined
<frame src="Entete.html"noresize scrolling="no">
✉
Line 95, column 15: there is no attribute "COLS"
<FRAMESET COLS="20%,70%">
✉
Line 95, column 24: element "FRAMESET" undefined
<FRAMESET COLS="20%,70%">
✉
Line 96, column 32: "NORESIZE" is not a member of a group specified for any attribute
<FRAME src="volet.html"noresize scrolling="auto">
✉
Line 96, column 48: element "FRAME" undefined
<FRAME src="volet.html"noresize scrolling="auto">
✉
Line 97, column 36: "NORESIZE" is not a member of a group specified for any attribute
<FRAME src="principale.html"noresize>
✉
Line 97, column 36: element "FRAME" undefined
<FRAME src="principale.html"noresize>
✉
Line 106, column 24: document type does not allow element "BODY" here
<body bgcolor="#FFFFFF"><div id="pubLay" style="position: absolute; top: 0px; r
✉
Line 127, column 6: end tag for "HTML" which is not finished
</html>
No DOCTYPE Found! Falling Back to HTML 4.01 TransitionalA DOCTYPE Declaration is mandatory for most current markup languages and without one it is impossible to reliably validate this document. I am falling back to "HTML 4.01 Transitional" and will attempt to validate the document anyway, but this is very likely to produce spurious error messages for most non-trivial documents.
So what should I do? Tell me more...
DOCTYPE Fallback in effect!
The DOCTYPE Declaration in your document was not recognized. This probably means that the Formal Public Identifier contains a spelling error, or that the Declaration is not using correct syntax. Validation has been performed using a default "fallback" Document Type Definition that closely resembles HTML 4.01 Transitional, but the document will not be Valid until you have corrected the problem with the DOCTYPE Declaration.
This page is not Valid HTML 4.01 Transitional!
Below are the results of attempting to parse this document with an SGML parser.
Line 4, column 0: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
<HTML>
The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with the HTML 4.01 Transitional DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.
✉
Line 8, column 29: required attribute "TYPE" not specified
<script language="javascript">
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
✉
Line 64, column 111: end tag for element "TITLE" which is not open
...r ception, produit du terroir.</TITLE>'+
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occured in a script section of your document, you should probably read this FAQ entry.
✉
Line 65, column 9: end tag for "SCRIPT" omitted, but its declaration does not permit this
'</HEAD><frameset rows="62,*" frameborder="0" border="0" framespacing="0" onlo
✉
Line 8, column 0: start tag was here
<script language="javascript">
Line 65, column 9: end tag for "HEAD" which is not finished
'</HEAD><frameset rows="62,*" frameborder="0" border="0" framespacing="0" onlo
Most likely, You nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element (e.g. 'ul') which requires a child element (e.g. 'li') that you did not include. Hence the parent element is "not finished", not complete.
✉
Line 65, column 25: there is no attribute "ROWS"
'</HEAD><frameset rows="62,*" frameborder="0" border="0" framespacing="0" onlo
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.
✉
Line 65, column 44: there is no attribute "FRAMEBORDER"
...AD><frameset rows="62,*" frameborder="0" border="0" framespacing="0" onload="
✉
Line 65, column 55: there is no attribute "BORDER"
...t rows="62,*" frameborder="0" border="0" framespacing="0" onload="setLoad()"
✉
Line 65, column 72: there is no attribute "FRAMESPACING"
...meborder="0" border="0" framespacing="0" onload="setLoad()" onunload="stopMov
✉
Line 65, column 83: there is no attribute "ONLOAD"
..." border="0" framespacing="0" onload="setLoad()" onunload="stopMove()">'+
✉
Line 65, column 104: there is no attribute "ONUNLOAD"
...cing="0" onload="setLoad()" onunload="stopMove()">'+
✉
Line 65, column 116: element "FRAMESET" undefined
...oad="setLoad()" onunload="stopMove()">'+
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), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
✉
Line 66, column 14: there is no attribute "SRC"
'<FRAME src="http://iquebec.ifrance.com/heberg/pub.htm?Time=1091634013&Nom=let
✉
Line 66, column 73: cannot generate system identifier for general entity "Nom"
...e.com/heberg/pub.htm?Time=1091634013&Nom=leterroirdelestrie&FRAME=1" name="pu
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.
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 66, column 73: general entity "Nom" not defined and no default entity
...e.com/heberg/pub.htm?Time=1091634013&Nom=leterroirdelestrie&FRAME=1" name="pu
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 66, column 76: reference to entity "Nom" for which no system identifier could be generated
...om/heberg/pub.htm?Time=1091634013&Nom=leterroirdelestrie&FRAME=1" name="pubfr
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 66, column 72: entity was defined here
...ce.com/heberg/pub.htm?Time=1091634013&Nom=leterroirdelestrie&FRAME=1" name="p
Line 66, column 96: cannot generate system identifier for general entity "FRAME"
...me=1091634013&Nom=leterroirdelestrie&FRAME=1" name="pubframe" scrolling="no"
✉
Line 66, column 96: general entity "FRAME" not defined and no default entity
...me=1091634013&Nom=leterroirdelestrie&FRAME=1" name="pubframe" scrolling="no"
✉
Line 66, column 101: reference to entity "FRAME" for which no system identifier could be generated
...91634013&Nom=leterroirdelestrie&FRAME=1" name="pubframe" scrolling="no" nores
✉
Line 66, column 95: entity was defined here
...ime=1091634013&Nom=leterroirdelestrie&FRAME=1" name="pubframe" scrolling="no"
Line 66, column 110: there is no attribute "NAME"
...Nom=leterroirdelestrie&FRAME=1" name="pubframe" scrolling="no" noresize frame
✉
Line 66, column 131: there is no attribute "SCROLLING"
...e&FRAME=1" name="pubframe" scrolling="no" noresize frameborder="0" border="0"
✉
Line 66, column 145: "NORESIZE" is not a member of a group specified for any attribute
...e="pubframe" scrolling="no" noresize frameborder="0" border="0" framespacing=
✉
Line 66, column 157: there is no attribute "FRAMEBORDER"
... scrolling="no" noresize frameborder="0" border="0" framespacing="0">'+
✉
Line 66, column 168: there is no attribute "BORDER"
..."no" noresize frameborder="0" border="0" framespacing="0">'+
✉
Line 66, column 185: there is no attribute "FRAMESPACING"
...meborder="0" border="0" framespacing="0">'+
✉
Line 66, column 188: element "FRAME" undefined
...order="0" border="0" framespacing="0">'+
✉
Line 67, column 95: element "FRAME" undefined
...order="0" border="0" framespacing="0">'+
✉
Line 76, column 8: end tag for element "SCRIPT" which is not open
</script>
✉
Line 81, column 2: "DOCTYPE" declaration not allowed in instance
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
✉
Line 83, column 15: document type does not allow element "HTML" here
<html lang="fr">
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 91, column 50: "NORESIZE" is not a member of a group specified for any attribute
<frame name="entete.html"src="pages.html"noresize scrolling="yes">
✉
Line 91, column 65: element "FRAME" undefined
...entete.html"src="pages.html"noresize scrolling="yes">
✉
Line 93, column 68: element "FRAMESET" undefined
...*"frameborder="yes"border="50%" framespacing="1%">
✉
Line 94, column 33: "NORESIZE" is not a member of a group specified for any attribute
<frame src="Entete.html"noresize scrolling="no">
✉
Line 94, column 47: element "FRAME" undefined
<frame src="Entete.html"noresize scrolling="no">
✉
Line 95, column 15: there is no attribute "COLS"
<FRAMESET COLS="20%,70%">
✉
Line 95, column 24: element "FRAMESET" undefined
<FRAMESET COLS="20%,70%">
✉
Line 96, column 32: "NORESIZE" is not a member of a group specified for any attribute
<FRAME src="volet.html"noresize scrolling="auto">
✉
Line 96, column 48: element "FRAME" undefined
<FRAME src="volet.html"noresize scrolling="auto">
✉
Line 97, column 36: "NORESIZE" is not a member of a group specified for any attribute
<FRAME src="principale.html"noresize>
✉
Line 97, column 36: element "FRAME" undefined
<FRAME src="principale.html"noresize>
✉
Line 106, column 24: document type does not allow element "BODY" here
<body bgcolor="#FFFFFF"><div id="pubLay" style="position: absolute; top: 0px; r
✉
Line 127, column 6: end tag for "HTML" which is not finished
</html>
-
Monique - WRInaute passionné
- Messages: 1545
- Inscription: 16 Sep 2002
le Mer Aoû 04, 2004 17:09
Oui jeanguy, le doctype et le charset (encodage des caractères) doit figurer sur toutes les pages.
Je ne sais pas quelle page tu as soumise au validateur, mais visiblement il s'agit d'une page avec des frames... pour lesquelles le doctype est différent.
Avant d'aller plus loin, je te recommande vivement la lecture de Ecrire une page Web, tu comprendras mieux où tu vas et ce que tu fais.
Je t'invite aussi à bien réfléchir au choix de ton hébergeur, d'autant plus qu'il s'agit d'un site commercial.
Je pense qu'un hébergeur payant (une offre de base, peu coûteuse, suffirait pour ton site) serait un bon investissement. Tu y gagnerais en crédibilité aux yeux des visiteurs, en qualité de référencement aussi.
Amicalement,
Monique
Je ne sais pas quelle page tu as soumise au validateur, mais visiblement il s'agit d'une page avec des frames... pour lesquelles le doctype est différent.
Avant d'aller plus loin, je te recommande vivement la lecture de Ecrire une page Web, tu comprendras mieux où tu vas et ce que tu fais.
Je t'invite aussi à bien réfléchir au choix de ton hébergeur, d'autant plus qu'il s'agit d'un site commercial.
Je pense qu'un hébergeur payant (une offre de base, peu coûteuse, suffirait pour ton site) serait un bon investissement. Tu y gagnerais en crédibilité aux yeux des visiteurs, en qualité de référencement aussi.
Amicalement,
Monique
-
WebRankInfo - Administrateur du site
- Messages: 18964
- Inscription: 19 Avr 2002
le Mer Aoû 04, 2004 17:11
jeanguy, si tu veux des messages en français, tu peux essayer ce validateur : http://www.validome.org/
Olivier
Olivier
-
Juxener - WRInaute discret
- Messages: 209
- Inscription: 17 Mar 2004
le Jeu Aoû 05, 2004 11:04
lol, bah WRI ça bug bien ton truc ^^ !
Alors que le W3C me dit valide XHTML1.1 Strict, ton truc me trouve plein de pb complétement farfelus :
- Le code PublicID ("-//W3C//DTD XHTML 1.1 STRICT//EN") trouvé dans la déclaration du DOCTYPE est inconnu.
- L'attribut `language` n'est pas autorisé dans la balise script.
- L'attribut `target` n'est pas autorisé dans la balise a.
- caractère de données n'est pas permis ici (il parle d'un tiret que j'ai mis entre deux liens).
lol, enfin bref c du n'importe quoi :d
Alors que le W3C me dit valide XHTML1.1 Strict, ton truc me trouve plein de pb complétement farfelus :
- Le code PublicID ("-//W3C//DTD XHTML 1.1 STRICT//EN") trouvé dans la déclaration du DOCTYPE est inconnu.
- L'attribut `language` n'est pas autorisé dans la balise script.
- L'attribut `target` n'est pas autorisé dans la balise a.
- caractère de données n'est pas permis ici (il parle d'un tiret que j'ai mis entre deux liens).
lol, enfin bref c du n'importe quoi :d
-
Juxener - WRInaute discret
- Messages: 209
- Inscription: 17 Mar 2004
le Jeu Aoû 05, 2004 12:36
C'est faux !
J'en ai effectivement déjà entendu parler, mais les faits sont bien là, en XHTML1.1 Strict, le validator du W3C valide les target="" !
Ca s'avére une belle rumeur...
Et comment voudrais-tu ouvrir dans une nouvelle page autrement ?
J'en ai effectivement déjà entendu parler, mais les faits sont bien là, en XHTML1.1 Strict, le validator du W3C valide les target="" !
Ca s'avére une belle rumeur...
Et comment voudrais-tu ouvrir dans une nouvelle page autrement ?
-
Bool - WRInaute passionné
- Messages: 1290
- Inscription: 26 Fév 2004
le Jeu Aoû 05, 2004 12:50
Non, c'est vrai, le target n'est valide que pour les frames, avec le "document-type" frameset (qui est basé sur le traditionnal il me semble).
Et justement, le fait d'ouvrir dans une nouvelle page est "mal vu" : le w3c préfère laisser le choix aux utilisateurs... J'admets que j'ai eu beaucoup de mal à comprendre ce choix au départ, mais je me suis fait une raison.
D'ailleurs, en HTML 4.01 Strict, XHTML 1.0 Strict et XHTML 1.1, le validateur W3C me répond systématiquement : there is no attribute "target"
Et justement, le fait d'ouvrir dans une nouvelle page est "mal vu" : le w3c préfère laisser le choix aux utilisateurs... J'admets que j'ai eu beaucoup de mal à comprendre ce choix au départ, mais je me suis fait une raison.
D'ailleurs, en HTML 4.01 Strict, XHTML 1.0 Strict et XHTML 1.1, le validateur W3C me répond systématiquement : there is no attribute "target"
-
Juxener - WRInaute discret
- Messages: 209
- Inscription: 17 Mar 2004
le Jeu Aoû 05, 2004 12:55
Bon, bin je t'invite à aller sur www.jsand.net , à le valider, à constater que le validator répond qu'il est valide XHTML1.1 Strict (à ce jour, il n'y pas pluc strict) et enfin à constater dans ma source que j'utilise des target="_blank".
Je ne crois que ce que je vois.
Je ne crois que ce que je vois.
-
Bool - WRInaute passionné
- Messages: 1290
- Inscription: 26 Fév 2004
le Jeu Aoû 05, 2004 13:04
Oui, j'ai vu. Je suppose qu'il s'agit tout simplement d'un bug du validateur....
Sur toutes mes pages que j'avais testé, le target était interdit (et ce depuis HTML 4.01 hein). Partout on te dira la même chose (Openweb entre autre).
Et comme on peut le voir sur le site www.w3.org, cet attribut ne fait pas parti des DTD XHTML 1.0/1.1 Strict, mais seulement dans leur version traditional et frameset.
Essaye avec une page ne contenant presque rien...
Sur toutes mes pages que j'avais testé, le target était interdit (et ce depuis HTML 4.01 hein). Partout on te dira la même chose (Openweb entre autre).
Et comme on peut le voir sur le site www.w3.org, cet attribut ne fait pas parti des DTD XHTML 1.0/1.1 Strict, mais seulement dans leur version traditional et frameset.
Essaye avec une page ne contenant presque rien...
33 messages
• Page 1 sur 3 • 1, 2, 3
Formation recommandée sur ce thème :
Formation REFERENCEMENT naturel Google : apprenez une méthode efficace pour optimiser à fond le référencement naturel dans Google de façon durable... Formation animée par Olivier Duffez et Fabien Facériès, experts en référencement naturel.
Tous les détails sur le site Ranking Metrics : programme, prix, dates et lieux, inscription en ligne.
Lectures recommandées sur ce thème :
Qui est en ligne
Utilisateurs parcourant ce forum: Aucun utilisateur enregistré et 0 invités
Contact
Confidentialité