Return-Path: <stefano@apache.org>
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 76932 invoked from network); 25 Jun 2002 09:31:35 -0000
Received: from unknown (HELO bluebox.betaversion.org) (62.110.41.207)
  by daedalus.apache.org with SMTP; 25 Jun 2002 09:31:35 -0000
Received: from apache.org (ppp-217-133-234-13.dialup.tiscali.it
 [217.133.234.13])
	by bluebox.betaversion.org (Postfix) with ESMTP id 9D4BF173A2E
	for <forrest-dev@xml.apache.org>; Tue, 25 Jun 2002 11:31:45 +0200 (CEST)
Message-ID: <3D182EA3.7B6AA967@apache.org>
Date: Tue, 25 Jun 2002 10:49:39 +0200
From: Stefano Mazzocchi <stefano@apache.org>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Re: [DTD] List attributes
References: <3D160B5D.1010007@yahoo.de> <3D1722B8.7FF48C41@apache.org>
 <3D176831.3070800@yahoo.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

"J.Pietschmann" wrote:
> 
> Stefano Mazzocchi wrote:
> >>  <ol>
> >>    <li>
> >>      <ol>
> >>        <li>stuff
> >>  ->
> >>    1.
> >>      a) stuff
> >>or
> >>    1.
> >>      1.1 stuff
> >
> >
> > Isn't this a style decision?
> >
> > I mean: shouldn't be the graphic designer to know *how* to format nested
> > lists?
> 
> It depends. If so, you'll get *all* lists numbered either
> one or the other way. 

Yes, this is correct.

> While the graphic designer should supply
> a default, I can imagine that the document writer sometimes
> wants to have a choice.

Hmmm, maybe... but I'm not that sure.
 
> This is especially the case for *nested* lists.

Yes, I see this.

> The
> presentation
>    1. kkkkk
>      a) sdfs
>      b) klrdjtlert
>    2. laber kram
>      i) guru do
>      ii) gnta lore
> may be conceived differently from
>    1. kkkkk
>      1.1. sdfs
>      1.2. klrdjtlert
>    2. laber kram
>      2.1. guru do
>      2.2. gnta lore
> The latter suggests the sublists adhere to a more common
> criteria than in the first case, where the sublists may
> express arbitrary independent choices.
> You can, of course introduce a new element for "hierachical
> nested lists" in order to distinguish it from arbritrary
> nested lists.

that would have redundant semantic, an attribute on <ol> seems like a
better solution to me.

Anyway, how do you envision this attribute to be? Something like

 <ol numbering="latin-small|latin-big|letters|numbers">

would be enough for your needs?
 
> Apart from this, there is still the question
>  > > Are there default rules how nested <ol> get numbered?
> Getting
>    1. kkkkk
>      1. sdfs
>      2. klrdjtlert
>    2. laber kram
>      1. guru do
>      2. gnta lore
> is a bit unimpressive, and can become confusing.

Agreed.
 
> Unfortunately, there are a few nested ordered lists in the
> FOP documentation, therefore I'd like to get an answer from
> the guardians of the DTDs.
> Well, the question applies to unordered lists too, I guess.

really? why? do you want to be able to specify the bullet graphic? I
would clearly disagree since this is a style concern.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------