On 7 Sep 2007, at 16:44, Rafael wrote:

>     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").

HTML 4.01 Strict disallows these, like XHTML 1.0 Strict does. XHTML  
1.0 Transitional allows them, like HTML 4.01 Transitional does. XHTML  
1.0 is merely a XML serialisation of HTML 4.01.

> # 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.

You can use lower-cased text in HTML, you can quote attributes in  
HTML. You aren't forced to, but you can (this may be what you're  
meaning, but it sounds like the you think you can't).

> # "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).

On the subject of XHTML 2 support, no browser is intending to support  
it whatsoever.


- Geoffrey Sneddon


______________________________________________________________________
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/

Reply via email to