Florian,
Yes, that is correct. However, while the rendition would be the same,
the structure is different. Depending on what you intend to represent in
your document, you might want to use one or the other. Breaking the list
in two is inly really useful if you want to put something in between.
An application that produces a non-visual rendition (e.g. a talking book
generator) could make good use of the added structural information, that
two list-items are part of the same list. Also alternative
representations for small screens might use that information for
optimizing the readability of their rendition.
/Lars
Florian Reuter wrote:
> Hi Lars,
>
> but couldn't you write
>
>
>
> as
>
>
>
>
> according to Oliver's proposal?
>
> So the list override is not _needed_, right?
>
>> I think the logic which you are trying to apply here is flawed.
> ...
>> Any specification will at least require an algorithm which works according to that specification.
>
> ;-) I guess we live in two different worlds. I agree that when you design a total new spec/way of numbering this is what
> is most easy to do.
> However I'm forced to live in a world where I have to deal with realities ;-( And one of the realities I have is to deal
> with interop with MS binaries and interop with WW.
>
> Where I disagree is that specifications have to require an algorithm in the imperative way as Olivers proposal does. In
> fact in my proposal this is not the case...
>
> Anyway. It's a TC decision. All I want is that all members understand the implications and that we get a clear
> specification of numbering in ODF1.2.
>
> ~Florian
>
>
>
>>>> Lars Oppermann