Fwd: [xml2rfc] 1.31 formatting nit

["George Jones" <eludom@gmail.com>]

Since some of you have documents with a similar XML genesis, this might
be helpful.

---George

---------- Forwarded message ----------
From: Elwyn Davies
 <elwynd@dial.pipex.com>
Date: Aug 26, 2006 10:24 AM
Subject: Re: [xml2rfc] 1.31 formatting nit
To: gmj@pobox.com
Cc: 
xml2rfc@lists.xml.resource.org

I was tangling with this one last night as well!

It seems that this rather obscure error message comes out when you don't
get the nesting of <t> and <list> elements right in 
1.31.
An improved error message would help!

If you look at the DTD you will find that:
1. You can't have a <list> as a direct child of a section.  It must be
inside a <t>
2. Neither <t> nor <list> can be directly nested (recursive) - the
<list> must be the child of a <t> and the <t> must be the child of a
<list> (sort of mutually recursive).

It appears that 1.30 was pretty permissive as regards what it allowed in
this area - I spent some time last night fixing some aged xml2rfc that
had <list> as a direct child of <section> - it processed OK on 1.30 but
1.31 barfed in exactly the way you quote.

Your problem is that your addition makes the added <t> a  child of the
existing one which is not allowed.

The approved solution is to use <vspace>.  Add <vspace blankLines="1" />
to provide the blank line you require.
(BTW <vspace blankLines="0" /> or just <vspace /> forces a line break
without an extra blank line.)

Regards,
Elwyn

George Jones wrote:
> Hi.  I have some .XML that worked fine in 1.30, but in 1.31 I get
>
> -----------snip here----------------
> pass 2...
> can't read "av(.STYLE)": no such element in array around input line 196
> ----------end snip---------------------
>
> The offending input appears to be:
>
> ----------snip again-------------
>         <list style="hanging">
>         <t hangText="Capability.">
> line 196>>>              <t>
>               The device provides a means to filter IP packets on any
> interface
>               implementing IP.
>               </t>
> ----------end snip again--------
>
> The extra <t>...</t>  was resulting in nicely formatted output with
> extra blank lines:
>
> -------------snip'''------------------------
> 3.1.  Select Traffic on All Interfaces
>
>    Capability.
>
>       The device provides a means to filter IP packets on any interface
>       implementing IP.
>
>    Supported Practices.
> ------------snip'''--------------------------
>
> whereas deleting the <t>..</t>, which make 1.31 happy with the input
> results
> in more ugly output:
> 3.1.  Select Traffic on All Interfaces
>
> ------------snip n--------------------
>    Capability.  The device provides a means to filter IP packets on any
>       interface implementing IP.
>
>    Supported Practices.
> ------------snip n--------------------
>
> What to do, what to do ?
>
> Thanks,
> ---George Jones
>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@lists.xml.resource.org
> http://lists.xml.resource.org/mailman/listinfo/xml2rfc
>