- From: Maurice Carey <maurice@thymeonline.com>
- Date: Fri, 22 Jun 2007 10:35:33 -0400
- To: HTML Working Group <public-html@w3.org>
On 6/22/07 5:19 AM, "Thomas Pike" <thomasp@opera.com> wrote: > > Maurice Carey wrote: >> On 6/21/07 11:20 AM, "Josh Sled" <jsled@asynchronous.org> wrote: >>>> JS> Also, I note the analog with <object type=...>. >>>> There is no analogy, >>>> because |type| of OBJECT specify technical characteristic, >>>> but |type| of _all_ tags at all specify semantic characteristic. >>> In the same way that <object type> specifies a technical characteristic (the >>> media type) of the referenced object, <code type> would specify a technical >>> characteristic (the media type) of the in-lined code. >> And then it would be easier for extension developers to write things the >> color code code blocks for people like me who spend a lot of time reading >> code on peoples web pages that's often not color coded. >> .... >> I'm not suggesting html have anything to do with defining color coding rules >> or anything of the sort. But I do agree that extra bit of important >> information would be Very useful to many people. > > While the information may indeed be useful for such things, would it not > better belong in the lang="" attribute? > > As far as I'm aware this is valid even now: > > <code lang="x-php"> > <?php echo "Hello world!" ?> > </code> :) I don't really care what attribute's called. I just want one for this purpose. If nobody has any objections to lang I'm o.k. with lang. Although I thought lang had to do with only spoken languages and not programming languages. -- :: thyme online ltd :: po box cb13650 nassau the bahamas :: website: http://www.thymeonline.com/ :: tel: 242 327-1864 fax: 242 377 1038
Received on Friday, 22 June 2007 14:35:55 UTC