Yes, correct for XHTML1.x, but I can't see it in your reference to http://www.w3.org/TR/xhtml2/mod-inline-text.html#sec_9.12.  All the font style elements have been removed in XHTML2.
 
It is better practice to stop using such elements, especially when there are other elements that serve the same purpose, but are more semantically correct and accessible.
 
You can code your XHTML1.x to be compatible with XHTML2, which when it becomes a recommendation and supported, will mean minimum maintenance by oneself and reap the benefits of future and backward compatibility.
 
I often have trouble dealing with the inconsistency of the various W3C specifications, as the W3C does itself.  I tend to focus more on the WAI specifications because they (to me) are more refined in this area, and teach on better practices.
 
It amazes me that this type of thing has been kept in when there is there is such a strong movement towards semantic and separating structure and presentation.
 
Geoff
-----Original Message-----
From: Mordechai Peller


Geoff Deering wrote:
It depends which DTD you are referencing as to whether they are deprecated
or not, but <U> is definitely deprecated in everything from HTML4 onwards.
And <B> and <I> are deprecated for future compatibility because they belong
in "Font Style Elements", which are all deprecated, as CSS should be used
for these.
  
You may want to recheck your facts. In Changes from XHTML 1.0 Strict it states: "Most significant is the removal of features that were deprecated." Since b and i are still there, it must mean that they weren't deprecated. Also, sub and sup are current;y valid XHTML2 with no listed plans to either deprecate or remove (http://www.w3.org/TR/xhtml2/mod-inline-text.html#sec_9.12.).

I do happen to agree that b and i shouldn't be used, but they are still 100% valid XHTML1.1.

Reply via email to