Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 36,
Column 58:
cannot generate system identifier for general entity "printsec"
…books.google.fr/books?id=XcF-YkxwOh4C&printsec=frontcover#v=onepage&q&f=false"…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 36,
Column 58:
general entity "printsec" not defined and no default entity
…books.google.fr/books?id=XcF-YkxwOh4C&printsec=frontcover#v=onepage&q&f=false"…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 36,
Column 66:
reference to entity "printsec" for which no system identifier could be generated
…ogle.fr/books?id=XcF-YkxwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'IN…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 36,
Column 57:
entity was defined here
…/books.google.fr/books?id=XcF-YkxwOh4C&printsec=frontcover#v=onepage&q&f=false……kxwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dict…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 36,
Column 88:
general entity "q" not defined and no default entity
…kxwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dict…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 36,
Column 89:
reference to entity "q" for which no system identifier could be generated
…xwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dicti…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 36,
Column 87:
entity was defined here
…YkxwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dic……wOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dictio…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 36,
Column 90:
general entity "f" not defined and no default entity
…wOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dictio…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 36,
Column 91:
reference to entity "f" for which no system identifier could be generated
…Oh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Diction…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 36,
Column 89:
entity was defined here
…xwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dicti……ogle.fr/books?id=2dVdcLaAhvMC&printsec=frontcover&dq=shimaore&source=bl&ots=CV…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 36,
Column 57:
entity was defined here
…/books.google.fr/books?id=XcF-YkxwOh4C&printsec=frontcover#v=onepage&q&f=false……s?id=2dVdcLaAhvMC&printsec=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&sig…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 38,
Column 78:
general entity "dq" not defined and no default entity
…s?id=2dVdcLaAhvMC&printsec=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&sig…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 38,
Column 80:
reference to entity "dq" for which no system identifier could be generated
…id=2dVdcLaAhvMC&printsec=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&sig=4…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 38,
Column 77:
entity was defined here
…ks?id=2dVdcLaAhvMC&printsec=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&si……AhvMC&printsec=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&sig=4r_WhRHQAaR…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 38,
Column 90:
general entity "source" not defined and no default entity
…AhvMC&printsec=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&sig=4r_WhRHQAaR…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 38,
Column 96:
reference to entity "source" for which no system identifier could be generated
…printsec=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&sig=4r_WhRHQAaRK1p-Q0…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 38,
Column 89:
entity was defined here
…aAhvMC&printsec=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&sig=4r_WhRHQAa……tsec=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&sig=4r_WhRHQAaRK1p-Q02SwW…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 38,
Column 100:
general entity "ots" not defined and no default entity
…tsec=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&sig=4r_WhRHQAaRK1p-Q02SwW…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 38,
Column 103:
reference to entity "ots" for which no system identifier could be generated
…c=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&sig=4r_WhRHQAaRK1p-Q02SwWNiz…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 38,
Column 99:
entity was defined here
…ntsec=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&sig=4r_WhRHQAaRK1p-Q02Sw……&dq=shimaore&source=bl&ots=CVQKle5NKq&sig=4r_WhRHQAaRK1p-Q02SwWNizpN0&hl=fr&ei…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 38,
Column 115:
general entity "sig" not defined and no default entity
…&dq=shimaore&source=bl&ots=CVQKle5NKq&sig=4r_WhRHQAaRK1p-Q02SwWNizpN0&hl=fr&ei…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 38,
Column 118:
reference to entity "sig" for which no system identifier could be generated
…=shimaore&source=bl&ots=CVQKle5NKq&sig=4r_WhRHQAaRK1p-Q02SwWNizpN0&hl=fr&ei=_e…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 38,
Column 114:
entity was defined here
…r&dq=shimaore&source=bl&ots=CVQKle5NKq&sig=4r_WhRHQAaRK1p-Q02SwWNizpN0&hl=fr&e……e5NKq&sig=4r_WhRHQAaRK1p-Q02SwWNizpN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=bo…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 38,
Column 147:
general entity "hl" not defined and no default entity
…e5NKq&sig=4r_WhRHQAaRK1p-Q02SwWNizpN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=bo…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 38,
Column 149:
reference to entity "hl" for which no system identifier could be generated
…NKq&sig=4r_WhRHQAaRK1p-Q02SwWNizpN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book…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 38,
Column 146:
entity was defined here
…le5NKq&sig=4r_WhRHQAaRK1p-Q02SwWNizpN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=b……sig=4r_WhRHQAaRK1p-Q02SwWNizpN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book_res…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 38,
Column 153:
general entity "ei" not defined and no default entity
…sig=4r_WhRHQAaRK1p-Q02SwWNizpN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book_res…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 38,
Column 155:
reference to entity "ei" for which no system identifier could be generated
…g=4r_WhRHQAaRK1p-Q02SwWNizpN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book_resul…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 38,
Column 152:
entity was defined here
…&sig=4r_WhRHQAaRK1p-Q02SwWNizpN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book_re……WNizpN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&v…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 38,
Column 177:
general entity "sa" not defined and no default entity
…WNizpN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&v…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 38,
Column 179:
reference to entity "sa" for which no system identifier could be generated
…izpN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&ved…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 38,
Column 176:
entity was defined here
…wWNizpN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&……N0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&ved=0C…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 38,
Column 182:
general entity "oi" not defined and no default entity
…N0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&ved=0C…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 38,
Column 184:
reference to entity "oi" for which no system identifier could be generated
…&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&ved=0CFs…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 38,
Column 181:
entity was defined here
…pN0&hl=fr&ei=_eCyTdAkkafxA4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&ved=0……yTdAkkafxA4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&ved=0CFsQ6AEwCA#v=one…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 38,
Column 197:
general entity "ct" not defined and no default entity
…yTdAkkafxA4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&ved=0CFsQ6AEwCA#v=one…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 38,
Column 199:
reference to entity "ct" for which no system identifier could be generated
…dAkkafxA4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&ved=0CFsQ6AEwCA#v=onepa…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 38,
Column 196:
entity was defined here
…CyTdAkkafxA4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&ved=0CFsQ6AEwCA#v=on……4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&ved=0CFsQ6AEwCA#v=onepage&q&f=f…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 38,
Column 207:
general entity "resnum" not defined and no default entity
…4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&ved=0CFsQ6AEwCA#v=onepage&q&f=f…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 38,
Column 213:
reference to entity "resnum" for which no system identifier could be generated
…M&sa=X&oi=book_result&ct=result&resnum=9&ved=0CFsQ6AEwCA#v=onepage&q&f=false">…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 38,
Column 206:
entity was defined here
…A4nszJYM&sa=X&oi=book_result&ct=result&resnum=9&ved=0CFsQ6AEwCA#v=onepage&q&f=……a=X&oi=book_result&ct=result&resnum=9&ved=0CFsQ6AEwCA#v=onepage&q&f=false"><u>…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 38,
Column 216:
general entity "ved" not defined and no default entity
…a=X&oi=book_result&ct=result&resnum=9&ved=0CFsQ6AEwCA#v=onepage&q&f=false"><u>…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 38,
Column 219:
reference to entity "ved" for which no system identifier could be generated
…&oi=book_result&ct=result&resnum=9&ved=0CFsQ6AEwCA#v=onepage&q&f=false"><u>LE …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 38,
Column 215:
entity was defined here
…sa=X&oi=book_result&ct=result&resnum=9&ved=0CFsQ6AEwCA#v=onepage&q&f=false"><u……t&resnum=9&ved=0CFsQ6AEwCA#v=onepage&q&f=false"><u>LE SHIMAORE - Premiè…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 36,
Column 87:
entity was defined here
…YkxwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dic……resnum=9&ved=0CFsQ6AEwCA#v=onepage&q&f=false"><u>LE SHIMAORE - Première…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 36,
Column 89:
entity was defined here
…xwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dicti……ogle.fr/books?id=TXcUyZ9AZ4kC&printsec=frontcover&dq=related:ISBN2738450016&as…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 36,
Column 57:
entity was defined here
…/books.google.fr/books?id=XcF-YkxwOh4C&printsec=frontcover#v=onepage&q&f=false……id=TXcUyZ9AZ4kC&printsec=frontcover&dq=related:ISBN2738450016&as_brr=3#v=onepa…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 38,
Column 77:
entity was defined here
…ks?id=2dVdcLaAhvMC&printsec=frontcover&dq=shimaore&source=bl&ots=CVQKle5NKq&si……=frontcover&dq=related:ISBN2738450016&as_brr=3#v=onepage&q&f=false"><u>FURUKOM…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 41,
Column 104:
general entity "as_brr" not defined and no default entity
…=frontcover&dq=related:ISBN2738450016&as_brr=3#v=onepage&q&f=false"><u>FURUKOM…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 41,
Column 110:
reference to entity "as_brr" for which no system identifier could be generated
…cover&dq=related:ISBN2738450016&as_brr=3#v=onepage&q&f=false"><u>FURUKOMBE et …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 41,
Column 103:
entity was defined here
…c=frontcover&dq=related:ISBN2738450016&as_brr=3#v=onepage&q&f=false"><u>FURUKO……ed:ISBN2738450016&as_brr=3#v=onepage&q&f=false"><u>FURUKOMBE et autres Contes …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 36,
Column 87:
entity was defined here
…YkxwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dic……:ISBN2738450016&as_brr=3#v=onepage&q&f=false"><u>FURUKOMBE et autres Contes de…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 36,
Column 89:
entity was defined here
…xwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dicti……ogle.fr/books?id=nd3iesyBOKsC&printsec=frontcover#v=onepage&q&f=false"><u>DICT…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 36,
Column 57:
entity was defined here
…/books.google.fr/books?id=XcF-YkxwOh4C&printsec=frontcover#v=onepage&q&f=false……yBOKsC&printsec=frontcover#v=onepage&q&f=false"><u>DICTIONNAIRE FRANÇAI…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 36,
Column 87:
entity was defined here
…YkxwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dic……OKsC&printsec=frontcover#v=onepage&q&f=false"><u>DICTIONNAIRE FRANÇAIS …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 36,
Column 89:
entity was defined here
…xwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dicti……ogle.fr/books?id=G3pTE3PWpIYC&printsec=frontcover#v=onepage&q&f=false"><u>LEXI…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 36,
Column 57:
entity was defined here
…/books.google.fr/books?id=XcF-YkxwOh4C&printsec=frontcover#v=onepage&q&f=false……PWpIYC&printsec=frontcover#v=onepage&q&f=false"><u>LEXIQUE COMORIEN - FRAN&Cce…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 36,
Column 87:
entity was defined here
…YkxwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dic……pIYC&printsec=frontcover#v=onepage&q&f=false"><u>LEXIQUE COMORIEN - FRAN&Ccedi…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 36,
Column 89:
entity was defined here
…xwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dicti……ogle.fr/books?id=vjrqIBpGLSEC&printsec=frontcover#v=onepage&q&f=false"><u>LEXI…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 36,
Column 57:
entity was defined here
…/books.google.fr/books?id=XcF-YkxwOh4C&printsec=frontcover#v=onepage&q&f=false……pGLSEC&printsec=frontcover#v=onepage&q&f=false"><u>LEXIQUE FRANÇAIS COM…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 36,
Column 87:
entity was defined here
…YkxwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dic……LSEC&printsec=frontcover#v=onepage&q&f=false"><u>LEXIQUE FRANÇAIS COMOR…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 36,
Column 89:
entity was defined here
…xwOh4C&printsec=frontcover#v=onepage&q&f=false"><u>L'INTERPRÈTE - Dicti…