OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [office] Re: [office-comment] Re: my comments on the numberingspec proposal discussed by David F. andFlorian R.


Hi Florian,

Florian Reuter wrote:
> Hi,
> 
> for me the result it not so clear. Michael was refering to the HTML lists. However HTML lists simple can't numbering like 1., 1.1, 1.2, .... So the behaviour at this point is undefined.

HTML allows nested lists. Paragraphs contained in nested ODF lists get 
the same numbers as in HTML.

What HTML does not have is a feature that allows to display the number 
of upper levels in addition to the one of the current level. So, HTML 
provides a clue what number a certain list item gets, but indeed not how 
upper levels are displayed.

My comment regarding HTML you are referring to here actually applied to 
the question when numbering restarts. That's what we were discussing in 
that mail. It did not apply to the question how upper levels are displayed.

> 
> In fact my intuitive result would be
> 1.
> 1.i.
> 1.ii.
> 
> Regarding your answer at 2007-01-22. That was for :
> <list style-name="LS1">
> <list-item>
> <p>..<p>
> <list style-name="LS2">
>  <list-item> <p>..<p> </list-item>
> </list>
> <list style-name="LS3">
>   <list-item> <p>..<p> </list-item>
> </list>
> <list style-name="LS4">
>   <list-item>  <p>..<p> </list-item>
>  </list>
> </list-item>
> </list>
>  I guess.
> 
> which causes a restart of the lists. However for answer to the two types seems to be consistent.
> 
> 
> I really believe that Michaels hint to HTML does not help here, since HTML can't do this types of lists (right?). And we can derive both semantics from the HTML spec :-)

Partially right. See above. HTML tells you which numbers certain list 
items get. HTML does not tell you whether and how the numbers of upper 
levels are displayed.

> 
> So we should clarify this in the spec. And I would vote for a "single level overrride" semantic.

We may clarify this in the spec. But how does this relate to a "single 
level overrride" semantic?

> 
> 
> ~Florian
> 
> P.S.
> Can anybody with real :-) HTML knowledge please veriy my statement what 1, 1.1, 1.2, numbering of hierarchical lists on HTML is not possible. Thx.

It's not possible.

Michael
> 
> 
> 
>>>> Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems <Oliver-Rainer.Wittmann@Sun.COM> 01/29/07 1:20 PM >>>
> Florian Reuter wrote:
>> Hi,
>>
>> just wanted to get the list understanding phase restarted. 
>>
>> Is there a common sense what the following list definition will lead to?
>>
>> LS1=< {"1"/1}, {"1"/2}, {"1"/3}, {"1"/4}, … >
>> LS2=< {"1"/1}, {"A"/2}, {"1"/3}, {"1"/4}, … >
>> LS3=< {"A"/1}, {"i"/2}, {"1"/3}, {"1"/4}, … >
>> LS4=< {"i"/1}, {"a"/2}, {"1"/3}, {"1"/4}, … >
>>
>> <list style-name="LS1">
>> <list-item>
>>   <p>..<p>
>>   <list style-name="LS3">
>>    <list-item> <p>..<p> </list-item>
>>    <list-item> <p>..<p> </list-item>
>>  </list>
>> </list-item>
>> </list>
>>
>> Will it be
>> 1.
>> 1.i.
>> 1.ii.
>>
>> -- or --
>> 1.
>> A.i.
>> A.ii.
>>
>> or something completely different?
>>
> 
> 
> Hi,
> 
> For me it's:
> 
> 1.
> A.i.
> A.ii.
> 
> as David, Michael and I already answered at 2007-01-22.
> 
> Regards, Oliver.
> 


-- 
Michael Brauer, Technical Architect Software Engineering
StarOffice/OpenOffice.org
Sun Microsystems GmbH             Nagelsweg 55
D-20097 Hamburg, Germany          michael.brauer@sun.com
http://sun.com/staroffice         +49 40 23646 500
http://blogs.sun.com/GullFOSS



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]