zurück zur Startseite
  


Zurück XHTMLforum > (X)HTML und CSS > (X)HTML
Seite neu laden Nicht valieder Code von Map24

Antwort
 
LinkBack Themen-Optionen Ansicht
  #1 (permalink)  
Alt 06.11.2005, 18:52
Benutzerbild von sveniboy
Benutzer
neuer user
Thread-Ersteller
 
Registriert seit: 27.03.2005
Beiträge: 63
sveniboy befindet sich auf einem aufstrebenden Ast
Standard Nicht valieder Code von Map24

Hallole,
ich habe in meiner Page folgenden Code von Map24 mit eingebaut:
Code:
<iframe src="http://www.de.map24.com/source/link2map/v2.0.0/cnt_pick_code.php?amplinksection=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&dcountry=de&ddescription=Heides+Frisurenstudio%3Cbr%3EEberf%C3%BCrststra%C3%9Fe+5%3Cbr%3E74246+Eberstadt-+Klingenhof+%28DE%29" width="200" height="241" scrolling="no" frameborder=0></iframe>
Nun habe ich aber ein großes Prob...wenn ich meine Site nach W3C- Standard validiere, dann bekomme ich ca. 15 Fehlermeldungen. Wie bekomme ich diesen Code valide? Eigentlich darf man ja ihn nicht modifizieren! Besten Dank für jeden Tipp[/code]
Mit Zitat antworten
Sponsored Links
  #2 (permalink)  
Alt 06.11.2005, 19:09
Erfahrener Benutzer
XHTMLforum-Mitglied
 
Registriert seit: 19.07.2005
Beiträge: 211
Cyberman befindet sich auf einem aufstrebenden Ast
Standard

Ein Link auf die Seite wäre hilfreich.

Was genau bemängelt der Validator?

In jedem Fall würde ich die "&"-Zeichen durch "&amp;" ersetzen.
Mit Zitat antworten
Sponsored Links
  #3 (permalink)  
Alt 06.11.2005, 19:14
Benutzerbild von sveniboy
Benutzer
neuer user
Thread-Ersteller
 
Registriert seit: 27.03.2005
Beiträge: 63
sveniboy befindet sich auf einem aufstrebenden Ast
Standard

Das funzt aber net! Ich bekomme folgende Fehlermeldung wenn ich das "&" durch "&amp" ersetze:

FEHLER: Sie haben keine Link-ID "lid" übergeben. Ihre Maske kann nicht generiert werden.
ERROR while generating code: Parameter "lid" missed.
ERREUR: Le Parametre "lid" n'est pas la.

Die Site ist noch offline! Deshalb kann ich sie nicht zeigen.
Eine Liste der Fehler...bitteschön:
Code:
  Markup Validation Service
v0.7.1 
•	Skip Navigation | Home
•	About...
•	News
•	Docs
•	Help & FAQ
•	Feedback
•	Link Checker
Jump To: 
•	Results
Result:	Failed validation, 15 errors 
File:	upload://Form Submission
Modified:	
Server:	
Size:	
Content-Type:	
Encoding:	utf-8
Doctype:	XHTML 1.0 Transitional
Root Namespace:	http://www.w3.org/1999/xhtml

Note: The Validator XML support has some limitations. 
This page is not Valid XHTML 1.0 Transitional!
Below are the results of checking this document for XML well-formedness and validity. 
1.	Warning Line 63 column 104: cannot generate system identifier for general entity "lid".
...k_code.php?linksection=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%B
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 "&amp;" (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 &aelig; 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. 
✉ 
2.	Error Line 63 column 104: general entity "lid" not defined and no default entity.
...k_code.php?linksection=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%B
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. 
✉ 
3.	Warning Line 63 column 107: reference not terminated by REFC delimiter.
...ode.php?linksection=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrs
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. 
✉ 
4.	Warning Line 63 column 107: reference to external entity in attribute value.
...ode.php?linksection=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrs
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 '&amp;'. 
✉ 
5.	Error Line 63 column 107: reference to entity "lid" for which no system identifier could be generated.
...ode.php?linksection=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrs
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. 
✉ 
6.	Info Line 63 column 103: entity was defined here.
...ck_code.php?linksection=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%
7.	Warning Line 63 column 117: cannot generate system identifier for general entity "ol".
...nksection=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%9
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 "&amp;" (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 &aelig; 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. 
✉ 
8.	Error Line 63 column 117: general entity "ol" not defined and no default entity.
...nksection=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%9
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. 
✉ 
9.	Warning Line 63 column 119: reference not terminated by REFC delimiter.
...section=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%9Fe
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. 
✉ 
10.	Warning Line 63 column 119: reference to external entity in attribute value.
...section=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%9Fe
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 '&amp;'. 
✉ 
11.	Error Line 63 column 119: reference to entity "ol" for which no system identifier could be generated.
...section=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%9Fe
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. 
✉ 
12.	Info Line 63 column 116: entity was defined here.
...inksection=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%
13.	Warning Line 63 column 126: cannot generate system identifier for general entity "dstreet".
...=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%9Fe+5&dzip
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 "&amp;" (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 &aelig; 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. 
✉ 
14.	Error Line 63 column 126: general entity "dstreet" not defined and no default entity.
...=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%9Fe+5&dzip
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. 
✉ 
15.	Warning Line 63 column 133: reference not terminated by REFC delimiter.
...stroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%9Fe+5&dzip=74246&
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. 
✉ 
16.	Warning Line 63 column 133: reference to external entity in attribute value.
...stroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%9Fe+5&dzip=74246&
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 '&amp;'. 
✉ 
17.	Error Line 63 column 133: reference to entity "dstreet" for which no system identifier could be generated.
...stroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%9Fe+5&dzip=74246&
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. 
✉ 
18.	Info Line 63 column 125: entity was defined here.
...n=linkdestroute&lid=0f8488fc&ol=de-de&dstreet=Eberf%C3%BCrststra%C3%9Fe+5&dzi
19.	Warning Line 63 column 162: cannot generate system identifier for general entity "dzip".
...&dstreet=Eberf%C3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&d
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 "&amp;" (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 &aelig; 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. 
✉ 
20.	Error Line 63 column 162: general entity "dzip" not defined and no default entity.
...&dstreet=Eberf%C3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&d
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. 
✉ 
21.	Warning Line 63 column 166: reference not terminated by REFC delimiter.
...reet=Eberf%C3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&dcoun
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. 
✉ 
22.	Warning Line 63 column 166: reference to external entity in attribute value.
...reet=Eberf%C3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&dcoun
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 '&amp;'. 
✉ 
23.	Error Line 63 column 166: reference to entity "dzip" for which no system identifier could be generated.
...reet=Eberf%C3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&dcoun
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. 
✉ 
24.	Info Line 63 column 161: entity was defined here.
...e&dstreet=Eberf%C3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&
25.	Warning Line 63 column 173: cannot generate system identifier for general entity "dcity".
...erf%C3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&dcountry=de&
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 "&amp;" (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 &aelig; 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. 
✉ 
26.	Error Line 63 column 173: general entity "dcity" not defined and no default entity.
...erf%C3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&dcountry=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. 
✉ 
27.	Warning Line 63 column 178: reference not terminated by REFC delimiter.
...3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&dcountry=de&ddesc
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. 
✉ 
28.	Warning Line 63 column 178: reference to external entity in attribute value.
...3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&dcountry=de&ddesc
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 '&amp;'. 
✉ 
29.	Error Line 63 column 178: reference to entity "dcity" for which no system identifier could be generated.
...3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&dcountry=de&ddesc
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. 
✉ 
30.	Info Line 63 column 172: entity was defined here.
...berf%C3%BCrststra%C3%9Fe+5&dzip=74246&dcity=Eberstadt-+Klingenhof&dcountry=de
31.	Warning Line 63 column 201: cannot generate system identifier for general entity "dcountry".
...ip=74246&dcity=Eberstadt-+Klingenhof&dcountry=de&ddescription=Heides+Frisuren
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 "&amp;" (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 &aelig; 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. 
✉ 
32.	Error Line 63 column 201: general entity "dcountry" not defined and no default entity.
...ip=74246&dcity=Eberstadt-+Klingenhof&dcountry=de&ddescription=Heides+Frisuren
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. 
✉ 
33.	Warning Line 63 column 209: reference not terminated by REFC delimiter.
...&dcity=Eberstadt-+Klingenhof&dcountry=de&ddescription=Heides+Frisurenstudio%3
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. 
✉ 
34.	Warning Line 63 column 209: reference to external entity in attribute value.
...&dcity=Eberstadt-+Klingenhof&dcountry=de&ddescription=Heides+Frisurenstudio%3
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 '&amp;'. 
✉ 
35.	Error Line 63 column 209: reference to entity "dcountry" for which no system identifier could be generated.
...&dcity=Eberstadt-+Klingenhof&dcountry=de&ddescription=Heides+Frisurenstudio%3
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. 
✉ 
36.	Info Line 63 column 200: entity was defined here.
...zip=74246&dcity=Eberstadt-+Klingenhof&dcountry=de&ddescription=Heides+Frisure
37.	Warning Line 63 column 213: cannot generate system identifier for general entity "ddescription".
...ty=Eberstadt-+Klingenhof&dcountry=de&ddescription=Heides+Frisurenstudio%3Cbr%
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 "&amp;" (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 &aelig; 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. 
✉ 
38.	Error Line 63 column 213: general entity "ddescription" not defined and no default entity.
...ty=Eberstadt-+Klingenhof&dcountry=de&ddescription=Heides+Frisurenstudio%3Cbr%
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. 
✉ 
39.	Warning Line 63 column 225: reference not terminated by REFC delimiter.
...-+Klingenhof&dcountry=de&ddescription=Heides+Frisurenstudio%3Cbr%3EEberf%C3%B
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. 
✉ 
40.	Warning Line 63 column 225: reference to external entity in attribute value.
...-+Klingenhof&dcountry=de&ddescription=Heides+Frisurenstudio%3Cbr%3EEberf%C3%B
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 '&amp;'. 
✉ 
41.	Error Line 63 column 225: reference to entity "ddescription" for which no system identifier could be generated.
...-+Klingenhof&dcountry=de&ddescription=Heides+Frisurenstudio%3Cbr%3EEberf%C3%B
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. 
✉ 
42.	Info Line 63 column 212: entity was defined here.
...ity=Eberstadt-+Klingenhof&dcountry=de&ddescription=Heides+Frisurenstudio%3Cbr
43.	Error Line 63 column 380: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.
...ght="241" scrolling="no" frameborder=0></iframe>
✉ 
 The W3C Validator Team

Creez
Mit Zitat antworten
  #4 (permalink)  
Alt 06.11.2005, 19:32
Erfahrener Benutzer
XHTMLforum-Kenner
 
Registriert seit: 20.02.2005
Beiträge: 1.045
Tigereye befindet sich auf einem aufstrebenden Ast
Standard

Zitat:
Das funzt aber net! Ich bekomme folgende Fehlermeldung wenn ich das "&" durch "&amp" ersetze:
Du solltest es auch durch "&amp;" ersetzen, wie Cyberman gesagt hat
Kann sein, dass du das schon so gemacht hast und dich nur hier verschrieben hast, ich habe ehrlich gesagt nicht den ganzen Text vom Validator gelesen...
Außerdem solltest du all "&" in URLs durch "&amp;" ersetzen!
Mit Zitat antworten
  #5 (permalink)  
Alt 06.11.2005, 20:09
Benutzerbild von sveniboy
Benutzer
neuer user
Thread-Ersteller
 
Registriert seit: 27.03.2005
Beiträge: 63
sveniboy befindet sich auf einem aufstrebenden Ast
Standard

Das verflixte ";"...ich habe "&amp" anstatt "&amp;" geschrieben
Nun bekomme ich beim Validieren nur noch folgende Fehlermeldung.
Code:
Error  Line 63 column 408: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.
...ght="241" scrolling="no" frameborder=0></iframe>
Was kann ich hier tun, damit meine Site zu 100% valide wird??
Mit Zitat antworten
  #6 (permalink)  
Alt 06.11.2005, 20:16
Erfahrener Benutzer
XHTMLforum-Mitglied
 
Registriert seit: 19.07.2005
Beiträge: 211
Cyberman befindet sich auf einem aufstrebenden Ast
Standard

Gib Anführungszeichen(") um die Zahl Null bei "frameborder=".
In HTML müssen manche Werte als Literal(d.h. mit ") übergeben werden. Es ist nie falsch (soweit ich weiß) Werte mit " zu kennzeichnen. Daher am Besten immer machen.
Mit Zitat antworten
  #7 (permalink)  
Alt 06.11.2005, 20:17
Benutzerbild von Gumbo
XHTMLforum-Kenner
 
Registriert seit: 22.08.2004
Ort: Trier
Beiträge: 2.737
Gumbo ist jedem bekanntGumbo ist jedem bekanntGumbo ist jedem bekanntGumbo ist jedem bekanntGumbo ist jedem bekanntGumbo ist jedem bekannt
Standard

Attributwerte müssen in XHTML in Anführungszeichen stehen.
__________________
Markus Wulftange
Mit Zitat antworten
  #8 (permalink)  
Alt 06.11.2005, 20:19
Benutzerbild von sveniboy
Benutzer
neuer user
Thread-Ersteller
 
Registriert seit: 27.03.2005
Beiträge: 63
sveniboy befindet sich auf einem aufstrebenden Ast
Standard

@Cyberman & gumbo:
Viiiielen Dank...das wars Jetzt ist auch noch meine letzte Site valide. Wenn ich sie online habe, stelle ich mal den Link hier rein. Dann könnt ihr eure Meinung dazu preisgeben.
Bis denne :P
Mit Zitat antworten
Antwort

Themen-Optionen
Ansicht

Forumregeln
Es ist Ihnen nicht erlaubt, neue Themen zu verfassen.
Es ist Ihnen nicht erlaubt, auf Beiträge zu antworten.
Es ist Ihnen nicht erlaubt, Anhänge hochzuladen.
Es ist Ihnen nicht erlaubt, Ihre Beiträge zu bearbeiten.

BB-Code ist an.
Smileys sind an.
[IMG] Code ist an.
HTML-Code ist aus.
Trackbacks are an
Pingbacks are an
Refbacks are aus


Ähnliche Themen
Thema Autor Forum Antworten Letzter Beitrag
Was bedeutet folgender Code? web334 (X)HTML 3 24.07.2011 16:10
HTML mit PHP Code aus Datenbank auslesen + ausführen Garlandt Serveradministration und serverseitige Scripte 14 01.05.2011 13:45
CSS Code - Komme nicht zurecht Invator01 CSS 19 05.04.2011 22:00
Riesen Abstand aber nur bei dem ersten Eintrag (beim gleichen Code) StarSt0rm CSS 5 27.08.2007 16:01


Alle Zeitangaben in WEZ +2. Es ist jetzt 20:24 Uhr.