[xml2rfc] 1.31 formatting nit

[eludom at gmail.com (George Jones)]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://drakken.dbc.mtview.ca.us/pipermail/xml2rfc/attachments/20060826/5fda3670/attachment.htm
>From elwynd at dial.pipex.com  Sat Aug 26 16:24:44 2006
From: elwynd at dial.pipex.com (Elwyn Davies)
Date: Sat Aug 26 07:21:41 2006
Subject: [xml2rfc] 1.31 formatting nit
In-Reply-To: <[e-mail]>
References: <[e-mail]>
Message-ID: <[e-mail]>

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
> [e-mail]
> http://lists.xml.resource.org/mailman/listinfo/xml2rfc
>   
>From julian.reschke at gmx.de  Sat Aug 26 18:46:00 2006
From: julian.reschke at gmx.de (Julian Reschke)
Date: Sat Aug 26 08:46:02 2006
Subject: [xml2rfc] 1.31 formatting nit
In-Reply-To: <[e-mail]>
References: <[e-mail]>
	<[e-mail]>
Message-ID: <[e-mail]>

Hi,

two comments:

1) Run your input through a conforming and validating XML parser before 
giving it xml2rfc. This really can safe you lot of time later.

2) That being said, people want paragraph breaks in list items. We 
really should fix the rfc2629 DTD in some way to allow this, so people 
don't have to fall back to ugly hacks such as <vspace> (which is 
presentational, not semantical markup).

Best regards, Julian
>From mrose at dbc.mtview.ca.us  Sun Aug 27 21:44:53 2006
From: mrose at dbc.mtview.ca.us (Marshall Rose)
Date: Sun Aug 27 10:55:33 2006
Subject: [xml2rfc] 1.31 formatting nit
In-Reply-To: <[e-mail]>
References: <[e-mail]>
	<[e-mail]>
Message-ID: <[e-mail]>

> 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!

the next version will have a better error message.

regardless, you really ought to be using

	<?rfc string='yes' ?>

/mtr