fyi – in English we generally say "at 9 years old, ....", instead of the normal German "with 9 years" (a rare case where the english version is more wordy than the german!). I heard that a lot when I was in germany last year. |
I saw Jake's post yesterday. Can anyone tell a non-IT or Search guy what the results mean?
TonyB |
Tony – read this post http://blogoscoped.com/archive/2006-08-10-n50.html and the comments about it http://blogoscoped.com/forum/61418.html
Those numbers are mistakes in pages source code. Those errors are of course very unprofessional.
|
I switched back and forth between "at" and "with" not sure which is correct, and finally settled on "with"... good to know :) |
Edit: I changed from "errors" to "HTML syntax errors" to clarify in response to TonyB's comment. |
I have to admit a lot of the post and comments that Ludwik linked to were over my head.
Are you guys saying it's Google's fault for the errors, or the fault of the pages Google is indexing for search?
I realize not everyone agrees with each other on this one.
Tony |
TonyB, the HTML specifications provide the standard for how HTML should be done. If everyone writes markup conforming to the specifications, the chances of interoperability between tools (browsers, search engines etc) is maximised. According to the W3C validator (http://validator.w3.org), the markup at http://google.com contains 43 errors. Google's fault, and they really should know better. |
Thanks for the explaination, Danny.
TonyB |
Danny, the W3C valid HTML is ideal only if every browser the page will be viewed on is W3C compliant as well. Internet Explorer for instance is very far from W3C compliant, so in order to make a page look the same on multiple browsers with multiple different levels of W3C implimentation sometimes takes some creative HTML. One common method of making one page look the same in multiple browsers is by doing things that certain browsers will fail/ignore and that others won't. That way, you can feed certain browsers certain bits of HTML and other browsers other bits.
While this kind of thing can wreak havoc on your W3C compatability, it actually makes your page work better on multiple browsers.
Its not Google's fault, if you want to blame someone, blame Microsoft for starting the whole idea of limited compability. |
