W3C home > Mailing lists > Public > www-html@w3.org > November 2003

Re: The <blockcode> and <l> elements

From: Lachlan Hunt <lhunt07@postoffice.csu.edu.au>
Date: Fri, 7 Nov 2003 16:27:12 +1100
To: www-html@w3.org
Message-id: <3fab2d30.3fe8.0@postoffice.csu.edu.au>

>> 1. ELEMENT blockcode (l)* OR
>I wouldn't change it.
><p>This is really interesting stuff.</p>
>Marking up LaTeX or XHTML using XHTML in a <blockcode/> while also 
>demonstrating the results of the markup.

Why not use:
    <l class="h">&lt;h&gt;\chapter{introduction}&lt;/h&gt;</l>
    <l class="p">&lt;p&gt;This is really interesting stuff.&lt;/p&gt;</l>

  Using class selectors and CSS, the formatting can be demonstrated without
losing the semantics of code.
  However, demonstrating output should be done using the <samp> element, or
the future <blocksamp> element, which, as I can gather from previous threads,
might be included in the next draft.

<snip/> (some example code)

> I don't see why there mustn't ever be any markup within <blockcode/> 
>outside <l/> elements.
>For instance, in Java, I could want to use the class declaration as a 
>blockcode heading:
><h><span class="modifier">public</span> <span class="modifier">class</span>

>Hello {</h>
><!-- ... -->
  Semantically, I don't think this would be a heading.  Presentationally it
might be, which can be done using class selectors and CSS as described above.

  OR, place the heading ouside the blockcode element:
<h>Java Class Header</h>

  The bottom line is that all code is plain text.  Many editors do present code
using different colours (which can be done using <span>, or other inline elements),
but, semantically, it's still all plain text.
Received on Friday, 7 November 2003 00:27:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:06:06 UTC