docbook-apps

  • 1.  Profiling on table columns

    Posted 12-13-2012 15:45
      |   view attached
    Hello all,

    I didn't find anything relevant about this topic, but I am facing this
    very same problem. A table from which I need to filter out columns...
    Did anyone solve this?
    I thought the profiling attribute could be set on the colspec, and then
    removing the corresponding entries shouldn't be that hard, but dealing
    with spans might be a cause of major headaches.

    Anyone already tried?

    Have a nice day,

    --
    NeoDoc
    Camille Bégnis
    Gérant
    camille@neodoc.fr <mailto:camille@neodoc.fr>
    Tél: +33(0)9.54.96.99.55 - Fax: +33(0)9.59.96.99.55
    http://www.neodoc.fr/
    5, rue de la Touloubre
    13770 Venelles
    France

    </mailto:camille@neodoc.fr>


  • 2.  Re: [docbook-apps] Profiling on table columns

    Posted 12-13-2012 16:26
    On 13.12.2012 16:44, Camille Bégnis wrote:

    > I didn't find anything relevant about this topic, but I am facing this very same
    > problem. A table from which I need to filter out columns...
    > Did anyone solve this?
    > I thought the profiling attribute could be set on the colspec, and then removing
    > the corresponding entries shouldn't be that hard, but dealing with spans might
    > be a cause of major headaches.

    Profiling is "dumb" it doesn't know anything about content of elements.
    So if you want to profile whole column you have to put profiling
    attribute on each entry in this column. Also if you use CALS tables you
    need to adjust cols attribute on tgroup element. And of course spans
    will be the most difficult task.

    So in some cases it can be quite straightforward, in some cases it would
    be very difficult.

    Jirka


    --
    ------------------------------------------------------------------
    Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz
    ------------------------------------------------------------------
    Professional XML consulting and training services
    DocBook customization, custom XSLT/XSL-FO document processing
    ------------------------------------------------------------------
    OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
    ------------------------------------------------------------------
    Bringing you XML Prague conference http://xmlprague.cz
    ------------------------------------------------------------------




  • 3.  Re: [docbook-apps] Profiling on table columns

    Posted 12-13-2012 17:33
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    On 12/13/2012 10:26 AM, Jirka Kosek wrote:
    > So in some cases it can be quite straightforward, in some cases it
    > would be very difficult.

    Another difficulty is that you might also need/want to adjust column
    widths.

    Another approach would be to store the content in a custom semantic
    format suited to the data and transform it into a CALS or HTML table
    as a preprocessing step as part of the build, then xinclude the table
    into your doc. The preprocessing step could include/exclude data based
    on profiling inputs. The custom format might be easier to understand
    and edit than a CALS or HTML table as well.

    David

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.11 (GNU/Linux)
    Comment: Using GnuPG with undefined - http://www.enigmail.net/

    iQEcBAEBAgAGBQJQyhEyAAoJEMHeSXG7afUhBKQH/3M9RvNb0+LtkYFKOgBgYNtY
    fwXak0AeBe19krl/90EQny8LPzCOQ4m+lkf2NaP/kEO/YQQD4j8/8gtVyb3dlfQ4
    h0FqgOLuBNiK6MBZgX76jJmJv/ZR2xnkpJMF8Sq2BYnMXIihCkxdMJlflsO+2xF5
    f4/aTeZzg7dIlo7hDZCVLYXGO+SogjwhXFYkwaEoTk7qwgPklND5cSsnglPTKW7b
    Lnh03l+waGCWwcGtWkXsObrKENCwiL7ZfeTg1CXj7qTbTFzAqxO0SuQa06maydNA
    mw0+qm04wvSkrToIGbuRp7UUIt2cBIQLbX/OT+p3vlsc4uvT3YGMh74JjN9SpMo=
    =D/39
    -----END PGP SIGNATURE-----



  • 4.  Re: [docbook-apps] Profiling on table columns

    Posted 12-14-2012 09:10
    Thanks Jirka, David,

    I'll try to make a simple table data structure indeed, and a short
    customization for this specific usecase.

    Best regards,

    --
    NeoDoc
    Camille Bégnis

    On 13/12/2012 18:32, David Cramer wrote:
    > On 12/13/2012 10:26 AM, Jirka Kosek wrote:
    > > So in some cases it can be quite straightforward, in some cases it
    > > would be very difficult.
    >
    > Another difficulty is that you might also need/want to adjust column
    > widths.
    >
    > Another approach would be to store the content in a custom semantic
    > format suited to the data and transform it into a CALS or HTML table
    > as a preprocessing step as part of the build, then xinclude the table
    > into your doc. The preprocessing step could include/exclude data based
    > on profiling inputs. The custom format might be easier to understand
    > and edit than a CALS or HTML table as well.
    >
    > David
    >
    >