Callout lists

[nelliemckesson]

How do we want to style these? I don't like having them in tables, but was there a specific reason for that? This is probably only a problem we need to solve internally, and not something we need to build into the spec.

I went ahead and did this for now:

    <ol class="calloutlist">
      <li><p><a href="#CO3-1"><img " src="callouts/1.pdf" alt="1"/></a> This directory holds MS-DOS.</p></li>

      <li><p><a href="#CO3-2">
          <img " src="callouts/2.pdf" alt="2"/></a> <a href="#CO3-3">
          <img " src="callouts/3.pdf" alt="3"/></a> <a href="#CO3-4">
          <img " src="callouts/4.pdf" alt="4"/></a> System startup code for DOS. <strong>
          [Too much whitespace; confusing to readers]</strong></p></li>

      <li><p><a href="#CO3-5"><img " src="callouts/5.pdf" alt="5"/></a> Some sort of Windows 3.1 hack.</p></li>
    </ol>

[adamwitwer]

Ha, I wondered which one of us would be the first to ask about callout lists. :)

Table seems unnecessary, I agree. Also, consider using Unicode values instead of images?

[nelliemckesson]

ooh unicode, i like that idea if we can make it work

[adamwitwer]

Cool, I'll test it at some point.

Note to self: U+2776-U+277F or (preferably) U+278A-U+2793

[sandersk]

Yeah, I would love to use Unicode for the markers instead of images. The main reason I haven't pushed for that in EPUB is that I was concerned that many ereading systems wouldn't support the characters. But maybe that's not the case :)

[sandersk]

Right now, for initial release of the spec, there's no formally specified way for doing callout lists in HTMLBook, which means that folks can use whatever markup and classes they like.

We should further discuss whether more formal requirements are needed for future drafts of the spec