#460 list/@type="unordered" is not recommended, but used often


The definition of list/@type suggests these values:

list items are numbered or lettered.
list items are marked with a bullet or other typographic device.
list items are not numbered or bulleted. [Default]
each list item glosses some term or concept, which is given by a label element preceding the list item.

However, the stylesheets are peppered with uses of "unordered" (which used to be in there, but is not any more). These should be replaced with "bulleted", presumably.


Bugs: #460


<< < 1 2 3 4 .. 6 > >> (Page 2 of 6)
  • Martin Holmes

    Martin Holmes - 2013-01-05

    I see this was set to red, but I hope that doesn't result in its getting lost. We have a manifest inconsistency in the Guidelines at the moment, so we should get that fixed asap. We should make sure this is on the list for discussion at the next ftf.

  • Sebastian Rahtz

    Sebastian Rahtz - 2013-01-05

    i think it has to be RED, because there is no simple agreed solution. I do agree it needs a f2f discusson and decision

  • Lou Burnard

    Lou Burnard - 2013-01-19

    Making practice in the Guidelines consistent should not be very hard though. Here's the complete list of @type values currently used and their frequencies

    attendance 2
    bullets 4
    encoders 3
    gloss 85
    index 2
    indexentry 1
    inline 1
    ordered 57
    simple 119
    speakers 8
    unordered 2
    參與者 1
    編碼員 1

  • Sebastian Rahtz

    Sebastian Rahtz - 2013-01-20

    I'd certainly be in favour of getting rid of type=bullets, easy enough. Its the type="simple" ones which a bit harder. According to the Spec, this means "simplelist items are not numbered or bulleted. ". Given the the Glines are a born-digital document, what does this mean? how should they be rendered, and how do you know there are a list if they have no number or symbol prefix? how do you know where items stop and start?

    It seems highly likely to me that type="simple" actually means "ordered"....

    I'll say again that I think the presence of "bullets" (as opposed to asterisks, emdashes, or arrows) should be encoding using @rend, and has no place in @type

  • Martin Holmes

    Martin Holmes - 2013-01-20

    "simple" is rendered as bullets in the Guidelines rendering, and it's clear from the contexts that "ordered" was not intended by the author (see for instance the lists of board and council members in the Preface).

  • Sebastian Rahtz

    Sebastian Rahtz - 2013-01-20

    yes, sorry, i meant "unordered" for "simple".

  • Lou Burnard

    Lou Burnard - 2013-02-06

    In the Guidelines, the only thing that matters is the distinction between explicitly numbered lists (which should be and I think all are @type="ordered"), glossary lists (which are all @type="gloss") and lists which are not numbered, which are variously @type="bullets", @type="unordered" and @type="simple" and @type="". Clearly we should make these consistent, and I propose that the easiest way of doing so would be to make them all either "simple" or "". My preference would be for the latter.

  • Sebastian Rahtz

    Sebastian Rahtz - 2013-02-06

    if we all agree that "ordered" and "gloss" make sense, then it seems to me we should promote and use "unorderded" rather than "simple". Why, you ask? cos a) whats the difference between "simple" and "unordered", and b) most modern systems make the ordered/unordered distinction, so we might as well use that vocabulary

    if of course someone can find a beautiful example of a simple list which is neither ordered not unordered, i'd like to see it...

  • Martin Holmes

    Martin Holmes - 2013-02-06

    One question is whether "unordered" = "bulleted". That's the case with HTML. We might argue that we're not interested in rendering here -- that bulleted vs numbered etc. should be expressed through @rend and @style, and now that we have @style, that's especially easy. But that leaves me wondering what "ordered" means, if not some kind of numbering.

  • Martin Holmes

    Martin Holmes - 2013-04-12
    • assigned_to: Sebastian Rahtz --> Martin Holmes
    • Group: RED --> AMBER
<< < 1 2 3 4 .. 6 > >> (Page 2 of 6)

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks