docbook-apps

  • 1.  Re: [docbook-apps] To Rene Hache, Larry Garfield, Bob Stayton, Jirka Kosek - About a former XHTML accessiblity project

    Posted 05-15-2007 15:48
    I've long wanted to make DocBook's XHTML cleaner, and I've started on it more than once. But my approach was too big, looking at the entire XHTML design, and so each time it was put off due to lack of time.

    As people have pointed out, perhaps only a few elements need to be changed. We could have a parameter (xhtml.clean?), and add xsl:choose statements to some element templates to produce alternate output if that parameter is set. What would really help me is a list of elements that need this treatment.

    Bob Stayton
    Sagehill Enterprises
    DocBook Consulting
    bobs@sagehill.net





  • 2.  Re: *** GMX Spamverdacht *** Re: [docbook-apps] To Rene Hache, Larry Garfield, Bob Stayton, Jirka Kosek - About a former XHTML accessiblity project

    Posted 05-15-2007 18:26
    El Martes, 15 de Mayo de 2007 17:47, Bob Stayton escribió:
    > I've long wanted to make DocBook's XHTML cleaner, and I've started on it
    > more than once. But my approach was too big, looking at the entire XHTML
    > design, and so each time it was put off due to lack of time.
    >
    > As people have pointed out, perhaps only a few elements need to be changed.
    > We could have a parameter (xhtml.clean?), and add xsl:choose statements to
    > some element templates to produce alternate output if that parameter is
    > set. What would really help me is a list of elements that need this
    > treatment.


    IMHO, the first step would be to create a set of XHTML pages containing how
    each DB element, and its attributes, should be mapped into XHTML-1.1 +
    Ascessibility (valid XHTML-1.1 could be served as valid XHTML-1.0 if needed
    for browsers compatibility).

    Having that example mapping to know the actual changes needed, can be
    evaluated if that xhtml.clean parameter could be used, if the current xhtml/
    templates could be full-changed to generate the new code, or if will be
    better to have two separate xhtml templates sets: the current one plus a new
    xhtml1.1 tree.




    --
    Manuel Canales Esparcia
    Usuario de LFS nº2886: http://www.linuxfromscratch.org
    LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info
    TLDP-ES: http://es.tldp.org



  • 3.  RE: [docbook-apps] To Rene Hache, Larry Garfield, Bob Stayton, Jirka Kosek - About a former XHTML accessiblity project

    Posted 06-06-2007 22:12
    Regarding the empty divs, what about a post-processing step (like one
    pass profiling, but on the other end) that processes the output and
    turns this:



    Into this:



    If you had a div with a class that had a child div with a class and the
    child div didn't have any following siblings, you could even combine the
    classes, to
    (assuming there were no conflicting
    attrs that couldn't be combined).

    I guess the places where tables are used are easily found. Here are the
    ones I see just looking around:

    variablelist (when list presentation is set to table...since this is an
    option already I guess the desire would be for a css-based tabular
    layout).
    calloutlist (when callout.list.table is 1. The alternative now is
    ,
    but those don't work well with callout graphics apparently)
    qandaset
    simplelist
    blockquote
    The headers and footers in chunked output
    funcprototype
    The viewport in process.image
    graphical admonitions

    David


    ________________________________

    From: Bob Stayton [mailto:
    bobs@sagehill.net]
    Sent: Tuesday, May 15, 2007 10:48 AM
    To: Wright, Barton; Nicolas RAINARD;
    docbook-apps@lists.oasis-open.org
    Subject: Re: [docbook-apps] To Rene Hache, Larry Garfield, Bob
    Stayton, Jirka Kosek - About a former XHTML accessiblity project


    I've long wanted to make DocBook's XHTML cleaner, and I've
    started on it more than once. But my approach was too big, looking at
    the entire XHTML design, and so each time it was put off due to lack of
    time.

    As people have pointed out, perhaps only a few elements need to
    be changed. We could have a parameter (xhtml.clean?), and add
    xsl:choose statements to some element templates to produce alternate
    output if that parameter is set. What would really help me is a list of
    elements that need this treatment.

    Bob Stayton
    Sagehill Enterprises
    DocBook Consulting
    bobs@sagehill.net