redneckboredom skrev:
använd inget program.. skriv i html iställe..sen kan du göra layouten och div gallerier i photoshop.. blir bra mkt bättre än nått program kan göra de.. + att de e inte speciellt svårtatt lära sej heller
Peace
ete
Testar man din hemsida hittar man följande:
No Character Encoding Found! Falling back to UTF-8.
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.
Read the FAQ entry on character encoding for more details and pointers on how to fix this problem with your document.
This page is not Valid HTML 4.01 Frameset!
Below are the results of attempting to parse this document with an SGML parser.
1. Error Line 33 column 54: document type does not allow element "SCRIPT" here.
<script type="text/javascript" language="JavaScript">
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
✉
2. Error Line 38 column 32: end tag for element "FRAMESET" which is not open.
document.write('</frameset>');
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.
✉
3. Error Line 41 column 11: document type does not allow element "NOSCRIPT" here.
<noscript>
✉
4. Error Line 42 column 38: there is no attribute "FRAMESPACING".
<frameset rows="*,1" framespacing="0" border="0" frameborder="NO">
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.
✉
5. Error Line 42 column 49: there is no attribute "BORDER".
<frameset rows="*,1" framespacing="0" border="0" frameborder="NO">
✉
6. Error Line 42 column 65: there is no attribute "FRAMEBORDER".
... rows="*,1" framespacing="0" border="0" frameborder="NO">
✉
7. Error Line 42 column 69: document type does not allow element "FRAMESET" here.
...,1" framespacing="0" border="0" frameborder="NO">
✉
8. Error Line 43 column 73: character data is not allowed here.
...ramespacing="0" border="0" frameborder="NO">');
You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>) or forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes).
✉
9. Warning Line 45 column 40: cannot generate system identifier for general entity "fldbannernr".
<frame src="/adstart?fldpromonr=4&fldbannernr=0&flddomainnr=6340906&ip=128
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.
✉
10. Error Line 45 column 40: general entity "fldbannernr" not defined and no default entity.
<frame src="/adstart?fldpromonr=4&fldbannernr=0&flddomainnr=6340906&ip=128
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.
✉
11. Error Line 45 column 51: reference to entity "fldbannernr" for which no system identifier could be generated.
...rc="/adstart?fldpromonr=4&fldbannernr=0&flddomainnr=6340906&ip=128.30.52.13&t
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 45 column 39: entity was defined here.
<frame src="/adstart?fldpromonr=4&fldbannernr=0&flddomainnr=6340906&ip=128
13. Warning Line 45 column 54: cannot generate system identifier for general entity "flddomainnr".
..."/adstart?fldpromonr=4&fldbannernr=0&flddomainnr=6340906&ip=128.30.52.13&tid=
✉
14. Error Line 45 column 54: general entity "flddomainnr" not defined and no default entity.
..."/adstart?fldpromonr=4&fldbannernr=0&flddomainnr=6340906&ip=128.30.52.13&tid=
✉
15. Error Line 45 column 65: reference to entity "flddomainnr" for which no system identifier could be generated.
...ldpromonr=4&fldbannernr=0&flddomainnr=6340906&ip=128.30.52.13&tid=11325676921
✉
16. Info Line 45 column 53: entity was defined here.
...="/adstart?fldpromonr=4&fldbannernr=0&flddomainnr=6340906&ip=128.30.52.13&tid
17. Warning Line 45 column 74: cannot generate system identifier for general entity "ip".
...=4&fldbannernr=0&flddomainnr=6340906&ip=128.30.52.13&tid=1132567692193&fwurl=
....och så här fortsätter det fram till fel nummer 37
37. Error Line 47 column 12: end tag for "FRAMESET" omitted, but its declaration does not permit this.
</noscript>
* You forgot to close a tag, or
* you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.
✉
38. Info Line 42 column 4: start tag was here.
<frameset rows="*,1" framespacing="0" border="0" frameborder="NO">
39. Error Line 48 column 6: end tag for "HTML" which is not finished.
</html>
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 which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, <head> generally requires a <title>, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
...tycker det verkar vara vanskligt att köra helt på egen hand.....
