[Boost-docs] using <auto-index-verbose>on causes invalid index.xml

Subject: [Boost-docs] using <auto-index-verbose>on causes invalid index.xml
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2011-01-26 15:34:18

I have used 

<auto-index-verbose>on

successfully on some docs builds, but with Pool, I find that switching it on
causes invalid xml in index.xml  (missing closing tags):

file:///I%3A/boost-sandbox/guild/pool/libs/pool/doc/bin/msvc-10.0/debug/auto
-index-internal-on/auto-index-verbose-on/auto-index-on/threading-multi/autod
oc-xml/index.xml:222: parser error : Opening and ending tag mismatch:
compound line 158 and doxygenindex
</doxygenindex>

file:///I%3A/boost-sandbox/guild/pool/libs/pool/doc/bin/msvc-10.0/debug/auto
-index-internal-on/auto-index-verbose-on/auto-index-on/threading-multi/autod
oc-xml/index.xml:223: parser error : Premature end of data in tag compound
line 151

and others similar

and thus

unable to parse
I:\boost-sandbox\guild\pool\libs\pool\doc\bin\msvc-10.0\debug\auto-index-int
ernal-on\auto-index-verbose-on\auto-index-on\threading-multi\autodoc-xml\ind
ex.xml

But I have yet to put my finger on what is causing this for this docs
(Pool).

Is there anything I can do wrong with adding 

<auto-index-verbose>on

  inside

if --enable-index in  [ modules.peek : ARGV ]
{
   ECHO "Building the Pool docs with automatic index generation enabled." ;
   using auto-index ;
   project : requirements

    <auto-index>on

   <auto-index-verbose>on

     <format>html:<auto-index-internal>on  # on (or off) to use internally
generated indexes.

Are the syntax restrictions on where comments and/or new/blank lines can go?

Is <auto-index-verbose>on as well as or instead of <auto-index>on ?

Thanks

Paul
---
Paul A. Bristow,
Prizet Farmhouse, Kendal LA8 8AB  UK
[phone]  07714330204
pbristow_at_[hidden]