Re Oysters, when I inserted body tags, it made no difference, but when I
inserted <!DOCTYPE HTML>
the number of errors rose from 10 to 12. Conclusion, if it ain't broke,
don't fix it. My thanks though to Ever Hard for helping me sort out the
only file that was apparently causing browsers any trouble.
The only way to fix the problems is to fix the problems.
I have given you a fully corrected version of the oysters file that has
no errors, validates completely, and uses your preferred font and bold
mark-up.
Of course using a doctype that deprecates the use of font, i and b will
increase the error count. This seems to be what you have done.
Declaring your file as a specific version of html will only reduce the
error count if the file is written according to that version of html. If
you define an html version for which your mark-up is even less compliant,
then of course the error count will increase.
You have remained deaf and blind to this every time you have brought your
recurring broken mark-up caused problems to us, and every time that we
have told you that your basic problems are:
Broken mark-up, specifically un-terminated elements for which termination
is compulsory.
Your refusal to address these fundamental html errors (which can be fixed
without using any css, despite the css advocacy that takes place here)
are why your broken html mark-up continues to break browsers.
Rgds
Denis McMahon
