Hi, Ta!
I'm not sure what you're talking about when you mention "the
forked-code wars", but chances are you're worrying unnecessarily.
As far as I see, he's only trying to get people actually understand
what XHTML is, and the differences it has against HTML, though I have a
somewhat different opinion regarding some of the "Myths" he describes,
it seems it's a subjective matter, for instance... (IMO)
# XHTML *does* promote more separation of content and presentation that
HTML does, since it doesn't allow most of the presentational attributes
anymore (e.g "align") and some of the presentation tags (e.g. "font").
# XHTML pages are not parsed as such, mainly because of a "really old"
but popular folk: IE 6 (not sure about IE 7, though). The rest, I
believe, are able to manage XHTML documents.
# XML parsers *don't have* to check for XHTML validity, XML is not XHTML
(though XHTML is XML).
# HTML is not deprecated, and its next version (5) looks like "the way
to go" instead of XHTML 2. Why? Because the genius at the W3C didn't
made XHTML 2 entirely backward compatible with XHTML 1.x --just great!
# "XHTML is not future compatible"... ¿¿?? Sorry, I don't get it. Future
compatible? What is? It's usually the other way around, "backward
compatible" --since everything evolves (or it should).
# "XHTML does not have good browser support"... I think he should have
tested this much more than I have (which is "just barely"), so I'll only
say that, as mentioned above, XHTML documents aren't sent like such to
browsers, but as HTML.
# Not parsing XHTML dramatically faster than HTML... I think that's
true. It still is faster, though, and there's less a probability of an
error because, simply because the parser "don't need to guess" how it
should threat this or that (or where an element is supposed to end).
# "XHTML is not extensible". Interesting... XML (Extensible Markup
Language) IS extensible because there isn't a set of tags or attributes
to use, you can define them on your own (as well as the DTD's). XHTML
has a fixed number of DTD's, so yes, it is not 'extensible'. On the
other hand, IIRC, it is designed to allow more than one 'namespace'
(just as XML do), so... it allows for "extensibility" (once it's "fully"
supported).
# XHTML source cleaner than HTML... not really, that depends on the guy
(or app) writing it. But it is easier to read (provided there is a good
indentation), not only because lower-cased text is easier to read than
upper-cased text and because the quotes help you identify the
attributes, but also because it *forces* you and everyone else to do so.
# "Using XHTML does not encourage better support by web browsers and it
is not a vote for a better web if you are..." etc.
Well, the problem here may be the context. If you read from "if you are
still supporting IE and various..." it has sense. He, once again, talks
about XHTML 2 not being backward compatible, which is true, but that
doesn't mean it's a dead end. XHTML 2 has some time on works, but I
don't know of any browser supporting it yet and even less of people
preparing their sites for it. Meaning, you can choose to stick with
XHTML 1.x and send them a message: backward compatibility is important,
what's the meaning of the current XHTML 1.x Transitional option then?.
If they ignore us, HTML is just waiting for another opportunity (with v5).
Anyway, it does this is a matter of perception. This is basically
what I know and how I see this topic. I actually think is unnecessary,
even more given the way he takes the topic, almost threatening the reader.
One of his points is that XHTML is not well supported (i.e. IE 6),
but he also says that M$ will support it in a future version. What's the
problem then? It's always been like that, CSS included.
Another one, XHTML 2 not been backward compatible. That's true, and
that's threatening any possible fast and painless XHTML 2 adoption, even
favoring HTML 5. It's still a draft, they still have the chance to
change this, but XHTML should evolve, there's nothing wrong with that
(as long as it has sense).
Don't forget that what we actually need is for browser vendors to
actually support those technologies, and that takes time. Where's CSS 3
right now? I've only seen a couple of browsers starting to support tiny
bits of it yet, but they're working on that, and someday we will be able
to relay on it (right, M$? right?).
Just my 2¢,
Rafael.
P.S. Sorry for the long message.
Tigdh Glesain wrote:
> Hallo Folks,
>
> I am just a little foncused. This may seem like an 'off-topic'
> subject, but I think I'm correct in saying it effects the way in
> which we code our CSS to a degree. If this topic has been covered
> before, then I apologise and would ask for a pointer towards the
> resource.
>
> This article, http://www.webdevout.net/articles/beware-of-
> xhtml#what_is_xhtml which was found while researching the the 3px IE
> bug has caused me to ponder, does this author have a point that is
> worthy of heeding.
>
> If I am writing good XHTML markup and 'matching' my css to a standard
> on par with my markup, am I being led down a path that may become a
> repeat of the "forked-code wars" of the late 1990s, et al?
>
> Am I worrying unnecessarily? Do any of have any 'jeez' to go with my
> 'whine'? (O:
>
> Can a more experienced head than mine soothe my troubled mind...
>
> Ta!
>
> ----------------------------------
> TAG
> [EMAIL PROTECTED]
>
>
>
> ______________________________________________________________________
> css-discuss [EMAIL PROTECTED]
> http://www.css-discuss.org/mailman/listinfo/css-d
> IE7 information -- http://css-discuss.incutio.com/?page=IE7
> List wiki/FAQ -- http://css-discuss.incutio.com/
> Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
>
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7 information -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/