Kenneth Johansson wrote:
> When I investigated the documents from the various revisions, none of them 
> had structural problems regarding captions. However, in
> the versions prior to v1.11 there were structural errors in the bookinfo 
> element. I've since then given very strict instructions and
> my writers know that they may not check in any invalid documents into cvs.

First of all, #PCDATA was added to the content model of
caption in 4.3.

Therefore, in a DocBook *4.2* document, a caption should be indented 
like this:
---
         <caption>
           <para>Component view of the Sectra Cardiology Package and its
           interaction with IDS5</para>
         </caption>
---



* This is the case in <section id="_Toc95720492"> of V1.8:
---
       <mediaobject>
         <imageobject>
           <imagedata 
fileref="images/installation_guide_angio_cardio-component_view.png"
                      format="PNG" />
         </imageobject>

         <caption>
           <para>Component view of the Sectra Cardiology Package and its
           interaction with IDS5</para>
         </caption>
       </mediaobject>
---



* This is *not* the case in <section id="_Toc95720492"> of V1.9:
---
       <mediaobject>
         <imageobject>
           <imagedata 
fileref="images/installation_guide_angio_cardio-component_view.png"
                      format="PNG" />
         </imageobject>

         <caption><para>Component view of the Sectra Cardiology Package 
and its
         interaction with IDS5</para></caption>
       </mediaobject>
---



* Possible explanation #1: In V1.9, an xi:include was added at the 
beginning of <chapter id="_Toc95720491">
--
<xi:include href="../user_guide/introduction/indications_for_use.xml"
                 xmlns:xi="http://www.w3.org/2001/XInclude"; />
--
and "indications_for_use.xml" is invalid.



* Possible explanation #2: Someone in your organization have modified 
your system-wide XML catalog to make
"-//OASIS//DTD DocBook XML V4.2//EN" point to a *V4.3* DTD (!!!).



---
PS: I don't think there is a bug related to this in XXE.



Reply via email to