HTML5 should *never *include specifications for what you're asking.  From an
pure HTML standpoint, you should never be specifying what type of numbering
scheme to use, just how to structure list items.  The context of *type* you
speak of is presentational.  Maybe a *class="legal"* attribute might assist
you.  Then it is for the CSS to specify the look.

If you're looking for pixel-perfect representation, that is *not* what
HTML/CSS or even Web browsers were intended to do.  A potential workaround
may be to offer an HTML version (with JavaScript to prefix the parent
section numbers in each list item <==> progressive enhancement), but if you
want to maintain the absolute original format, offer a PDF version.

A simple solution using inline CSS and JavaScript (ALWAYS separate them):

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; >
<head>
    <title>Legal Document</title>
    <style type="text/css">
        /*** KEEP THIS IN A SEPARATE FILE ***/
        ol.legal,
        ol.legal ol {                /* default display, one reference per
item */
            list-style-type: decimal;
            padding-left: 1em;
            margin-left: .5em;
        }
        body.ready ol.legal,
        body.ready ol.legal ol {    /* if JS enabled, allow it to specify
the reference numbers */
            list-style-type: none;
        }
        body.ready ol.legal {
            padding-left: 0;
        }

        body.ready ol.legal span.reference {
            padding-right: .5em;
        }
    </style>
    <!-- using jQuery for DOM traversal -->
   <script type="text/javascript"
    src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js";>
    </script>
    <script type="text/javascript">
        /*** KEEP THIS IN A SEPARATE FILE ***/
        $(function() {
            $('body').addClass('ready'); /* let CSS know that JS is enabled
*/

            $('ol.legal li')
                .each(function() {
                    /* each list item should also reference all of it's
ancestors' positions */
                    var $li = $(this);

                    $li
                        .prepend( /* add to beginning of each list item */
                            '<span class="reference">' +
                            $li
                                .parents('li')
                                .andSelf()
                                .map(function() { return
$(this).prevAll().size() + 1; }) /* map all reference positions as array */
                                .get()
                                .join('.')
                            + '</span>'
                        );
                });
        });
    </script>
</head>
<body>
    <h1>Document Name</h1>

    <!-- offer a PDF version if the user needs to see it in its ORIGINAL
format -->
    <p>A <a href="#">PDF version</a> is available.</p>

    <!-- only layout the structure of the legal document here.  CSS should
handle the rest -->
    <ol class="legal">
         <li>Blah Blah</li>
         <li>Blah Blah</li>
         <li>Blah Blah
              <ol>
                   <li>Blah Blah</li>
                   <li>Blah Blah</li>
                   <li>Blah Blah
                          <ol>
                                  <li>Blah blah</li>
                                  <li>Blah blah</li>
                                  <li>Blah blah</li>
                          </ol>
                   </li>
              </ol>
         </li>
    </ol>
</body>
</html>



Regards,
Jason T. Featheringham
Front-End Engineer
http://thejase.com

On Wed, Aug 26, 2009 at 10:11 AM, Jason Grant <ja...@flexewebs.com> wrote:

> Anthony - what's there to 'understand'? This is the semantically correct
> way to mark up this particular set of data.
> Simple as.
> By all means you should be able to style up looking pixel perfect the same
> across any browser under the Sun.
> Cheers,
> Jason
>
>
> On Wed, Aug 26, 2009 at 3:04 PM, Antony Gr. <ant.grak...@gmail.com> wrote:
>
>> IE not understand this. You don't agree?
>>
>> 2009/8/26 Jason Grant <ja...@flexewebs.com>:
>> > Inspect the TOC of this page and see that the markup I used is
>> essentially
>> > correct.
>> > The difference is that they wrote the numbers down into the page (i.e.
>> 1.1,
>> > 4.11, 5., etc.)
>> > http://www.w3.org/TR/xhtml1/
>> > If unsure, use a W3C page as a reference point :-)
>> > Cheers,
>> > Jason
>> >
>> >
>> >
>> >
>> > --
>> > Jason Grant BSc, MSc
>> > CEO, Flexewebs Ltd.
>> > www.flexewebs.com
>> > ja...@flexewebs.com
>> > +44 (0)7748 591 770
>> > Company no.: 5587469
>> >
>> > www.flexewebs.com/semantix
>> > www.twitter.com/flexewebs
>> > www.linkedin.com/in/flexewebs
>> >
>> > *******************************************************************
>> > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
>> > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
>> > Help: memberh...@webstandardsgroup.org
>> > *******************************************************************
>>
>>
>> *******************************************************************
>> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
>> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
>> Help: memberh...@webstandardsgroup.org
>> *******************************************************************
>>
>>
>
>
> --
> Jason Grant BSc, MSc
> CEO, Flexewebs Ltd.
> www.flexewebs.com
> ja...@flexewebs.com
> +44 (0)7748 591 770
> Company no.: 5587469
>
> www.flexewebs.com/semantix
> www.twitter.com/flexewebs
> www.linkedin.com/in/flexewebs
>
> *******************************************************************
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: memberh...@webstandardsgroup.org
> *******************************************************************
>


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************

Reply via email to