Hi, when traversing a document, I wonder how to check the type of a list. The docs say lists have types in OO1, and styles in OO2. But is there an example of how to check them? My current approach is this:

As you can see, for OO2 I have no idea. For OO1, I use the documented methods, but it turns out that they always report an ordered list, regardless if the list is ordered or not. This was tested with an SXW document (OO1 format), stored by OO 2. Thanks in advance Jochen

For OpenDocument, it seems there is no example, so I will try to investigate the styles and - as you write - decide which style indicates an ordered or unordered list. As OO2 must do this a similar way, there should be a pattern, I hope. For OO1, there is a problem. As you write, there should be ordered and unordered lists, but the OO::OODoc methods always report *ordered* lists for my document - regardless if the lists are ordered or not. Do I use the methods the wrong way, or is this a bug? How to do it correctly? Thanks!

1) Yes, OpenDocument is the OO2 format. Therefore, as OO2 *has* GUI buttons that toggle if the current paragraph is part of an ordered or an unordered list, when reading an OpenDocument list OO2 has to distinguish list paragraphs, and therefore it should use a certain pattern for the type decision. Say it treats a bullet prefix style attribute to handle the paragraph as part of a bullet list, and <whatever> prefix style attribute as an indicator that the list is ordered. Likewise, when a user presses the, say, "ordered list" button in OO2, it has to assign that certain prefix style attribute to the list element. So, as there must be an internal mapping in OO2 from prefix style attributes (bullets, numbers, whatever) to list types presented in the GUI (ordered, unordered) and vice versa, I hope I can find out this mapping pattern and use it similarly to detect the list types. Or, I'd be glad to hear about a standard OO2 method or code snippet to do this detection. As an optimization and suggestion, would it be possible to have builtin support of these mappings in the OO::OODoc methods isOrderedList() and isUnorderedList(), so when they detect they are called for an OpenDocument document they switch to that recognition method transparently? 2) I use the isOrderedList() method for a list element to find out its type. And yes, for my test document in OO1 format (exported by OO2), this method always returns true for ordered *and* unordered lists (I can send you the document to your CPAN author address, is this address still valid?). I tracked this down in the Perl debugger and found that finally OO::OODoc::Element::hasTag() returns true for "text:ordered-list", which in fact is what $node->getName() returns for $node. But nevertheless, the list is unordered, so ... ?

Thank you for this information. So it turns out at the moment there are three formats: OO1, OO2 Transitional, and OO2/OpenDocument, right? Thinking about this and your last sentence I think the consequence will be that I do not support OO1 and OO2 transitional in my tool, as OpenDocument is more universal (more applications using it) and the former two can be converted into OpenDocument by the free OO2 software. But it turns out OpenDocument has its pitfalls, too. In my example, I cannot find the style. What's wrong with my code?

This displays

So, I can find out that the internal style assigned to the bullet point is "L1", but how to find the style object for it? Thanks in advance!