Phantasy Star Cave Message Board

by **Malakai** » Tue Apr 12, 2005 6:31 am

Yes, it's 'easy', but it's also very time comsuming as some of the codes can be very long. Oh well, at least it's not binary coding. -_-

by **Myau Froto** » Wed Apr 13, 2005 1:34 am

Thanks you, and yes, I am in the process of learning HTML.

by **Shell Presto** » Wed Apr 13, 2005 1:45 am

it seems like you just forgot to save the files as html files. Personally, I have a hard time reading the content with the code popping up.I started a site 6 years ago and I remember how hard it was. Just go back and save the files as (name).html okay?(and it will get benoit off your back...)

by **Benoit** » Wed Apr 13, 2005 11:43 pm

<blockquote>Originally posted by LaconianShot For all he needs it for, a WYSIWYG editor works fine.</blockquote> A WYSIWYG editor should never be used for web page coding. You can be sure that it will generate non-standards-compliant code without fail.To illustrate, here's what the W3 validator gives for http://www.myaufroto.com/---No Character Encoding Found! Falling back to UTF-8.No DOCTYPE Found! Falling Back to HTML 4.01 TransitionalErrors: [TAB]32This page is not Valid HTML 4.01 Transitional!Below are the results of attempting to parse this document with an SGML parser. 1. Line 1, 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. ✉ 2. Line 14, column 80: required attribute "ALT" not specified ...x8.net/pro/pic/13263KIWbg/354283.jpg"></div> 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>. ✉ 3. Line 25, column 11: there is no attribute "SRC" <embed src="Dead.mp3" autostart="true" loop="true" width="2" height="0"> 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. ✉ 4. Line 25, column 32: there is no attribute "AUTOSTART" <embed src="Dead.mp3" autostart="true" loop="true" width="2" height="0"> ✉ 5. Line 25, column 44: there is no attribute "LOOP" <embed src="Dead.mp3" autostart="true" loop="true" width="2" height="0"> ✉ 6. Line 25, column 57: there is no attribute "WIDTH" <embed src="Dead.mp3" autostart="true" loop="true" width="2" height="0"> ✉ 7. Line 25, column 68: there is no attribute "HEIGHT" ...3" autostart="true" loop="true" width="2" height="0"> ✉ 8. Line 25, column 71: element "EMBED" undefined ...ostart="true" loop="true" width="2" height="0"> 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). ✉ 9. Line 27, column 8: element "NOEMBED" undefined <noembed> ✉ 10. Line 28, column 13: there is no attribute "SRC" <bgsound src="Dead.mp3" loop="infinite"> ✉ 11. Line 28, column 29: there is no attribute "LOOP" <bgsound src="Dead.mp3" loop="infinite"> ✉ 12. Line 28, column 39: element "BGSOUND" undefined <bgsound src="Dead.mp3" loop="infinite"> ✉ 13. Line 31, column 204: document type does not allow element "META" here ...mazing, playerworlds, genious, cheez"> 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). ✉ 14. Line 53, column 62: an attribute value must be a literal unless it contains only name characters ...="http://www.angelfire.com/punk5/hunkofcheez"><img src=</a> You have used a character that is not considered a "name character" in an attribute value. Which characters are considered...

by **Benoit** » Wed Apr 13, 2005 11:43 pm

16. Line 54, column 14: document type does not allow element "A" here <a href="slut">Wanna date me? Don't come off as a slut.(3/4/05)</a> ✉ 17. Line 55, column 19: document type does not allow element "A" here <a href="diversity">If you knew what diversity was, your wrong.(3/5/05)</a> ✉ 18. Line 56, column 17: document type does not allow element "A" here <a href="cocaine">Cocaine: The 'cool' thing. (3/6/05)</a> ✉ 19. Line 57, column 18: document type does not allow element "A" here <a href="phantasy">One game you'll never play. (3/7/05)</a> ✉ 20. Line 58, column 14: document type does not allow element "A" here <a href="bank">If you're going to open a bank account, don't go to Bank of Ameri ✉ 21. Line 59, column 14: document type does not allow element "A" here <a href="flip">For those of you who read my site...</a> ✉ 22. Line 60, column 18: document type does not allow element "A" here <a href="dumbitch">Girls, AIM names, their icons, and profiles: Making a point.( ✉ 23. Line 61, column 19: document type does not allow element "A" here <a href="realitytv">Reality TV: The equivilency of the coolness of me stepping i ✉ 24. Line 62, column 15: document type does not allow element "A" here <a href="page2">More shit to read....</a> ✉ 25. Line 63, column 2: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element. One possible cause for this message is that you have attempted to put a block-level element (such as "" or "<table>") inside an inline element (such as "<a>", "", or ""). ✉ 26. Line 67, column 7: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag <center><img src="/cgi-bin/Count.cgi"></center> ✉ 27. Line 67, column 37: required attribute "ALT" not specified <center><img src="/cgi-bin/Count.cgi"></center> ✉ 28. Line 68, column 2: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag ✉ 29. Line 72, column 7: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag <center>Email: <a href="mailto:[email protected]"> [email protected]</a></cent.. ✉ 30. Line 72, column 49: document type does not allow element "A" here <center>Email: <a href="mailto:[email protected]"> [email protected]</a></center> ✉ 31. Line 75, column 6: end tag for "A" omitted, but its declaration does not permit this </body> ✉ 32. Line 53, column 0: start tag was here <a href="http://www.angelfire.com/punk5/hunkofcheez"><img src=</a>

by **Tails99** » Thu Apr 14, 2005 1:14 am

<blockquote>Originally posted by BenoitYour website reeks of n00bish web page coding. Apparently you used Angelfire to generate your pages that are also improperly linked. </blockquote>Jeez, Benoit, do you always have to be bruatally honest like that?

by **LaconianShot** » Thu Apr 14, 2005 3:53 am

Great, the validator proves the point that I wasn't even argueing. Yes, his page is horrible for web standards, yes it's "n00bish", but come on... he's using a WYSIWYG editor for god sake. Doesn't that clue you in? He's obviously new at this, so give him some time to at least learn the actual coding before jumping on him. Or should I start nitpicking you? Last time I checked, you didn't use DOCTYPE declarations in your pages. They're "pointless and confusing", in your words, yet if I want to get nitpicky, I can tell you that the W3C heavily encourages the DOCTYPE declaration, and it is indeed necessary for web standards. How can you be preaching to him about using the hacks and work-arounds that a WYSIWYG editor offers when technically, you're doing the same thing by not using a DOCTYPE declaration? Now, you may not consciously be using the hacks and work-arounds that each browser supports, but by not including a DOCTYPE declaration, you're reverting the viewer's browser into "quirks" mode, in which all the browser specific hacks still work. This was done on the W3C's part simply because of all the web pages that were created before the concept of "web standards" came in. Really, you can only be web standard complient if you use a DOCTYPE declaration (which browsers do read). So if we want to get technical... you're hurting web standards. Now, I am by no means trying to get on your back about your site, which I find to be nicely coded, but if you want to nitpick this kid's first attempt at a site, I'll be inclined to nitpick yours. [size=small][Edit by LaconianShot on [TIME]1113450939[/TIME]][/size]

by **Lord Khyron** » Thu Apr 14, 2005 4:05 am

Hey Benoit, I ran your little validator on your page. Wanna know what it says?You're no better than him. I did your http://psoscript.netfirms.com/main.htmlLink. OMG! I found errors!Here is what it says: <blockquote>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. So what should I do? Tell me more...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 1, 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 11, column 22: there is no attribute "BACKGROUND"<table background="/nf-images/nf_back.gif" border="0" cellpadding="0" cellspYou 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). 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 15, column 98: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"...Hosting by Netfirms" align="absmiddle" border="0" src="/nf-images/FreewebhostThe value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed. ✉ Line 34, column 73: required attribute "ALT" not specified...osting.webhosting.asis" width="1" height="3"> 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 48, column 114: cannot generate system identifier for general entity "event"...ad/imp.gif?client=ca-netfirms_728x90&event=noscript"/> </noscript>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 48, column 114: general entity "event" not defined and no default entity...ad/imp.gif?client=ca-netfirms_728x90&event=noscript"/> </noscript>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 48, column 119: reference to entity "event" for which no system identifier could be generated[/quote]This is just a small example Benoit. You have no right to attack him if you won't follow your own "BELIEF".[size=small][Edit by Lord Khyron on [TIME]1113451845[/TIME]][/size]

by **Benoit** » Fri Apr 15, 2005 4:46 pm

<blockquote>Great, the validator proves the point that I wasn't even argueing. Yes, his page is horrible for web standards, yes it's "n00bish", but come on... he's using a WYSIWYG editor for god sake. Doesn't that clue you in? He's obviously new at this, so give him some time to at least learn the actual coding before jumping on him.</blockquote> As I said, first you learn to code and then you make a website. Did I ever use a WYSIWYG editor? Yes, for playing around. But I never made an actual site with it. I actually took the time to learn the basics of HTML, which don't require much time at all.To make something that resembles his website, he would have to learn only the HTML basics, which as I said, are learned very quickly. <blockquote>Or should I start nitpicking you? Last time I checked, you didn't use DOCTYPE declarations in your pages. They're "pointless and confusing", in your words, yet if I want to get nitpicky, I can tell you that the W3C heavily encourages the DOCTYPE declaration, and it is indeed necessary for web standards.</blockquote> Actually, I added DOCTYPE declarations a long time ago on my webring. However, I haven't gotten around to it on my script site yet. Probably because I've been neglecting it lately. <blockquote>Hey Benoit, I ran your little validator on your page. Wanna know what it says?You're no better than him. I did your http://psoscript.netfirms.com/main.htmlLink. OMG! I found errors!</blockquote> As usual, you don't pay much attention to reading. The errors you posted were errors in the HTML that my web host adds after uploading my page. It's something I have no control over.

by **LaconianShot** » Fri Apr 15, 2005 6:12 pm

<blockquote>As I said, first you learn to code and then you make a website.</blockquote> Your method, not everybody's. Web Design teachers teach the use of WYSIWYG before they teach you coding to get you familiar with the properties of a web page. Did you know that? Probably not. You know, there's cause for that. They wouldn't teach it in the curriculum if it didn't have merit.

by **Dorrinal Blackmantle** » Fri Apr 15, 2005 6:47 pm

Ever turn up your nose at some food that just plain looked nasty, whether it tasted good or was nutritious? It's about time you presented your content a little better. Don't ignore Benoit's content either, even though his presentation makes him out to be an asshole.

by **Benoit** » Fri Apr 15, 2005 10:22 pm

<blockquote>Originally posted by LaconianShot Your method, not everybody's. Web Design teachers teach the use of WYSIWYG before they teach you coding to get you familiar with the properties of a web page.</blockquote> Perhaps to get familiar with those things, but when you make a website to actually put it on the net, you code it.There are tons of people who never even get past the WYSIWIG because they don't learn the code. You really think they learn the code in class? Nope, they use shitty FrontPage or the more decent DreamWeaver.

by **LaconianShot** » Sat Apr 16, 2005 12:19 am

<blockquote>Perhaps to get familiar with those things, but when you make a website to actually put it on the net, you code it.</blockquote> Thank you for repeating exactly what I just said. <blockquote>You really think they learn the code in class? Nope, they use shitty FrontPage or the more decent DreamWeaver.</blockquote> Nope... you learn HTML. Perhaps not the latest version, but you do use coding instead of a WYSIWYG editor.

by **Benoit** » Sat Apr 16, 2005 4:44 pm

Alright, you got a point there. Seems we were saying almost the same thing.Now let me present you with a new point: not everyone follows Web-design classes, and knows these rules.

by **LaconianShot** » Sat Apr 16, 2005 8:48 pm

Sadly, that's a very true point. Now, I'm self-taught on HTML, XHTML and CSS, and have never really engaged in formal web design classes. Speaking from being self-taught, I have to say that the W3C is the best resource that I have access to, aside from a excellent HTML and CSS book. Sadly, a lot of people don't know about the W3C... if they did, we'd have standard compliant web pages. Then again, those who use WYSIWYG editors are using the deprecated coding that comes with the use of them. And deprecated code is getting eliminated as new browsers are being created. Eventually, I hope it's mandatory to be W3C compliant.

Phantasy Star Cave Message Board

My site.

My site.

My site.

My site.

My site.

My site.

My site.

My site.

My site.

My site.

My site.

My site.

My site.

My site.

My site.

My site.

Who is online