On Fri, 9 Nov 2001 21:54:22 -0500 (EST), Steve <[EMAIL PROTECTED]> wrote:
> [ s k i p ] > You can choose to use the "new version 4 HTML > standards" or continue to use whatever standard you're > comfortable with. > > If you use a DTD of HTML 2, AND your pages are > written to that standard, they'll validate... and > SHOULD render correctly on ANY browser. > > If you use a DTD of 3.2, AND write your pages to > that standard, they'll validate... and SHOULD > render correctly on any v.3 or higher browser. > > If you use a DTD of 4.0, AND use the elements from > that HTML set, they'll validate.... and SHOULD render > correctly on any v.4 browser. > OK but Arachne is AFAIK v1 browser ;-) should I write my pages in HTML 1.0? And, also AFAIK, Michael Polak never said anything about DTD the site has to follow if it is going to be browsed in Arachne. As long as my tags are rendered correctly, I don't care much about what DTD they validate in, if any. > Where you get into trouble is when you use the > DTD for 3.2 and sprinkle all kinds of tags from > 4.0 as you've done on your page. You need to > decide which standard you're going to use, and then > stick to it...at least within the page... feel free > to sprinkle all valid DTDs throughout your site. > Your use of the 3.2 DTD twice seems to cause problems > too. > Hmm... I have always thought that I may use any tagged content that is interpreted _de_facto_ correctly in the variety of browsers. I mean, okay, we have W3C standard, but it's not like the standard for what kilogram means, since there are no "standard browsers" around. Difference in rendering was what my unofficial buglist was to demonstrate. In Netscape and MSIE, even v4, you may actually use MIDDLE attribute anywhere as a synonym to CENTER, except CENTER tag, where CENTER is a tagname and not an attribute. > As you've probably seen, but I'll reiterate anyway: > Mithgol claims that <align=middle> doesn't work > correctly in Arachne, and gives us examples of tables > to prove it. > In the context of tables, THERE IS NO SUCH THING AS > <ALIGN=MIDDLE>, therefore Mithgol's assertion that > this is some kind of Arachne bug is completely without > merit. If he wishes to demonstrate Arachne bugs, it > MUST be with standard, valid HTML. Hmm... probably the word BUG was too rude for that? I mean THERE IS SUCH THING AS <ALIGN=MIDDLE>, and my examples did really prove that for MSIE and Netscape. There may not be valid comparison with FONT SIZE="red", as it was called about half a digest above. And if you're going to claim THERE IS NO SUCH THING AS <ALIGN=MIDDLE>, you should also claim that THERE IS NO WEB OUTSIDE ARACHNE. Using old HTML 3.2 tags inside HTML4-tagged content is what I think to be a good tradition of "graceful degradation" defined in AnyBrowser.Org. An unimplemented feature of MIDDLE==CENTER can be easily implemented by one line of C/C++ code, and I still hope it will be. It is as easy as it was with clearing all trailing spaces in URL, which was declared "a nasty trick" in Michael Polak's history.txt, but was nevertheless implemented. With that W3C validator, ARACHNE MSG was the first tag inside my buglist that was repeated to be unexisted. I think also that is among potentially divergentional tendencies for the Web, when one browser refuses to render what other browser do. BLINK and MARQUEE tags, for example. They are not in DTD, still they are useful. Arachne need more tags. > ... and now I'll steal one of Glenn's lines, and declare > that I've probably said too much on this already. ;-) That was your own choice to discuss it or not. I was not forcing you. Deeply yours, M M MM MM M M M I T H G O L M M http://mithgol.complife.net/ T H E [EMAIL PROTECTED] W W W W W E B M A S T E R W W W W W
