11. april 2005 - 13:43Der er
5 kommentarer og 1 løsning
Hvad er årsagen til validerignsfejlen
Hejsa
Jeg har prøvet at køre en side igennem w3c's validator... der kommer en bunke (hmm) fejlmeldinger. Den er især oppe og markerer hvergang der er et "&" i koden. Hvorfor nu det?
Et eksempel fra fejlrapporten: Line 367, column 1148: cannot generate system identifier for general entity "g1"
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.
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.
Det kan jeg ikke umiddelbart svare på - men jeg prøvede at stoppe din side gennem W3C's validator. Det første den brokker over, er: "No Character Encoding Found! Falling back to UTF-8.". Det tyder på, at du mangler et <meta>-tag i din <head>-sektion - noget ala dette:
Siden har ingen doctype, men en charset utf-8. (w3c validerer imod 4.01 transitional) Jeg har talt med en "kollega" omkring dette, her er et kort summering af hvad han sagde hvis andre skulle opleve det samme: -Han kan validerer både med lang og kort doctype. Så det er ikke der fejlen ligger i dette tilfælde. -hvis man prøver at konventerer linket til ASCII code validerer denne side fin *g*
Derfor tror jeg det er temmelig sansynligvis er fejlen afledt af en af de over 200 andre fejl i dukumentet. Tak for hjælpen.
Tilladte BB-code-tags: [b]fed[/b] [i]kursiv[/i] [u]understreget[/u] Web- og emailadresser omdannes automatisk til links. Der sættes "nofollow" på alle links.
