Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

The Easy Way to W3C Approval!!

sllort (442574) writes | more than 11 years ago

Slashdot.org 7

The absolute best way to to get the W3C to validate your site is to ban their IP address. Because, if your HTML doesn't check out, who's the wiser?

I'd like to take this opportunity to congratulate Rob & co on not having a gigantically flawed W3C validator page for the first time in their illustrious five-year history. Way to go, guys!

The absolute best way to to get the W3C to validate your site is to ban their IP address. Because, if your HTML doesn't check out, who's the wiser?

I'd like to take this opportunity to congratulate Rob & co on not having a gigantically flawed W3C validator page for the first time in their illustrious five-year history. Way to go, guys!

cancel ×

7 comments

Sorry! There are no comments related to the filter you selected.

Moo (1)

Chacham (981) | more than 11 years ago | (#6157612)

Heh

Yeah (1)

The Bungi (221687) | more than 11 years ago | (#6157812)

They've been doing it for ages. At least a year.

That's why I use HTML-Kit (1)

bofkentucky (555107) | more than 11 years ago | (#6158541)

Taco has repeatedly said he doesn't care as long as it displays in his browser, VA/OSDN have other ideas, but they let him run this workers paradise as his own.

BARF!! (0)

Anonymous Coward | more than 11 years ago | (#6162543)

Even when you do try to validate the ancient, broken code, it barfs anyhow. Thanks to the absence of character encoding.




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 validate the document. The sources I tried are:

  • The HTTP Content-Type field.
  • The XML Declaration.
  • The HTML "META" element.

And I even tried to autodetect it using the algorithm defined in Appendix F of the XML 1.0 Recommendation [w3.org] .

Since none of these sources yielded any usable information, I will not be able to validate this document. Sorry. Please make sure you specify the character encoding in use.

IANA [iana.org] maintains the list of official names for character sets [iana.org] .

Open Source at its Finest!! (1)

Pave Low (566880) | more than 11 years ago | (#6167462)

i wonder where's the YRO article about slashdot 'censoring' people from trying to validate their site?

Intentional or just poor programming? (1)

Safety Cap (253500) | more than 11 years ago | (#6178493)

D'yah think W3C got IP banned from someone messing with the validator, or do you think Slashkrew went out of their way? ;(

YES! (0)

Anonymous Coward | more than 11 years ago | (#6180362)



Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>