W3C home > Mailing lists > Public > xsl-editors@w3.org > July to September 2008

[Bug 6003] New: New type of lists

From: <bugzilla@wiggum.w3.org>
Date: Sat, 30 Aug 2008 12:18:58 +0000
To: xsl-editors@w3.org
Message-ID: <bug-6003-2197@http.www.w3.org/Bugs/Public/>


           Summary: New type of lists
           Product: XSLFO
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: XSL-FO 2.0 Requirements
        AssignedTo: xsl-editors@w3.org
        ReportedBy: j.tosovsky@tiscali.cz
         QAContact: xsl-editors@w3.org

At present, if definition lists are necessary, <fo:list-block> or <fo:table>
elements are used. 

In case of list-block the term is inserted into <fo:list-item-label> while
definition itself into <fo:list-item-body>. As for processing of
<fo:list-block> element a value of label witdh is required, it is set manualy
or computed (for the best results a quite complex formula is required).

In case of table the term is inserted into the first cell while definition into
second one. If nested definition list are necessary, nested tables are used.

These solutions have drawbacks - indentation in both cases is equal to the
width of term. If several levels of indentation are used, available width for
text itself very quickly decrease. We also never get nice design as indentation
of each level hasn't the same value. In case of <fo:list-block> such value can
be set manualy and hence it is possible to ensure the same value for each
level, but this idea goes against the automation.

In TeX different system is available:
Term is followed by definition (separated by space), but second line is
indented by arbitrary value - not according the width of term:

Term Definition. If definition
  is long, it continues on se-
  cond line a litle bit inden-
  ted. Nested term:
  Nested term Definition of 
    nested term keep the same
    value of indentation.

I haven't found any drawbacks, but advantages only: 
- much nicer design (imagine terms in bold)
- no problems with width of term
- enough width for definition text if several nested levels

This system seems to be idealy suited for automated processing so its
implementing should be high priority by my view.

I can imagine following structure:
<fo:definition-block start-indent="3em" provisional-label-separation="1em">

Three new elements and two current parameters are enough to XSL-FO processor to
build such output I think. It could improve design of many documents! Please
consider this carefuly.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Received on Saturday, 30 August 2008 12:19:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:25 UTC