docbook-apps

  • 1.  xinclude ...... of plain text?

    Posted 05-13-2009 14:47
    I'm wondering if I can use docbook (xml) to xinclude
    what is effectively a plain text file (all markup escaped).

    It's a configuration file I'd like to keep out of the xml
    till the last moment (to get it right)

    Any suggestions please?



    regards

    --
    Dave Pawson
    XSLT XSL-FO FAQ.
    http://www.dpawson.co.uk



  • 2.  RE: [docbook-apps] xinclude ...... of plain text?

    Posted 05-13-2009 16:32
    The xinclude syntax includes a parse attribute that indicates whether to treat as XML or text. A programlisting is designed for displaying files such as configuration files. Not sure if that is exactly what you were looking for.

    Larry Rowland


    Original Message


  • 3.  Re: [docbook-apps] xinclude ...... of plain text?

    Posted 05-13-2009 17:25
    Rowland, Larry wrote:
    > The xinclude syntax includes a parse attribute that indicates whether to treat as XML or text. A programlisting is designed for displaying files such as configuration files. Not sure if that is exactly what you were looking for.
    >
    > Larry Rowland


    Thanks Larry. RTFM was my real advice! v5 documentation tells me about it.

    As an alternative to using the textinsert element, consider using an
    Xinclude element with the parse="text" attribute and value specified, as
    detailed in DocBook XSL: TCG, Using XInclude for text inclusions.

    So

    <literallayout>
    <xi:include parse="text"
    href="build.properties" >
    <xi:fallback>
    <para><emphasis>FIXME: MISSING XINCLUDE CONTENT -
    build.properties</emphasis></para>
    </xi:fallback>
    </xi:include>
    </literallayout>



    regards

    --
    Dave Pawson
    XSLT XSL-FO FAQ.
    http://www.dpawson.co.uk



  • 4.  Re: [docbook-apps] xinclude ...... of plain text?

    Posted 05-13-2009 21:07
    On Wed, May 13, 2009 at 10:24 AM, DavePawson <davep@dpawson.co.uk> wrote:
    > As an alternative to using the textinsert element, consider using an
    > Xinclude element

    I'd argue that using XIncludes rather than textinsert increases the
    chances of interoperability. Here's Bob on the same:
    http://www.sagehill.net/docbookxsl/ModularDoc.html#XIncludePlainText



Related Content