[xml2rfc] 1.31 formatting nit
fenner at research.att.com (Bill Fenner) Wed, 30 August 2006 05:03 UTC
From: "fenner at research.att.com"
Date: Wed, 30 Aug 2006 05:03:27 +0000
Subject: [xml2rfc] 1.31 formatting nit
References: <c1468ac50608260546u59e5c80aj2ef5391b2c055de8@mail.gmail.com> <44F059AC.3090908@dial.pipex.com> <44F06CB8.7010508@gmx.de>
Message-ID: <200608301203.k7UC3KTE010320@bright.research.att.com>
X-Date: Wed Aug 30 05:03:27 2006
>1) Run your input through a conforming and validating XML parser before >giving it xml2rfc. This really can safe you lot of time later. Absolutely. If you don't have one of these handy, you can try mine: http://rtg.ietf.org/~fenner/ietf/xml2rfc-valid/ Alternately, xml2rfc contains one that it'll invoke if you use <?rfc strict="yes"?>. >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). I think this is sensible to brainstorm about, since it's something that has been asked for a lot. Something like: <!ELEMENT list (t+|lt+)> <!ELEMENT lt (t|list)+> <!ATTLIST lt hangText %ATEXT; #IMPLIED> Single-paragraph lists could still use <list><t>... for backwards compatability, new lists would be formatted with <lt>..</lt> wrappers around each item: <list><lt><t/><t/></lt><lt><t/></lt></list>? (A list should only be allowed to have t+ or lt+, not a mixture, to avoid confusion (always wrap or never wrap)) Bill >From julian.reschke at gmx.de Wed Aug 30 15:14:43 2006 From: julian.reschke at gmx.de (Julian Reschke) Date: Wed Aug 30 05:14:46 2006 Subject: [xml2rfc] 1.31 formatting nit In-Reply-To: <200608301203.k7UC3KTE010320@bright.research.att.com> References: <c1468ac50608260546u59e5c80aj2ef5391b2c055de8@mail.gmail.com> <44F059AC.3090908@dial.pipex.com> <44F06CB8.7010508@gmx.de> <200608301203.k7UC3KTE010320@bright.research.att.com> Message-ID: <44F58133.9060908@gmx.de> Bill Fenner schrieb: >> 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). > > I think this is sensible to brainstorm about, since it's something that > has been asked for a lot. Something like: > > <!ELEMENT list (t+|lt+)> > <!ELEMENT lt (t|list)+> > <!ATTLIST lt > hangText %ATEXT; #IMPLIED> > > Single-paragraph lists could still use <list><t>... for backwards > compatability, new lists would be formatted with <lt>..</lt> wrappers > around each item: > <list><lt><t/><t/></lt><lt><t/></lt></list>? > > (A list should only be allowed to have t+ or lt+, not a mixture, > to avoid confusion (always wrap or never wrap)) Sounds good to me. Best regards, Julian
- [xml2rfc] 1.31 formatting nit George Jones
- [xml2rfc] 1.31 formatting nit Elwyn Davies
- [xml2rfc] 1.31 formatting nit Joe Abley
- [xml2rfc] 1.31 formatting nit Joe Abley
- [xml2rfc] 1.31 formatting nit Bill Fenner
- [xml2rfc] 1.31 formatting nit Elwyn Davies
- [xml2rfc] DTD modifications for multi-paragraph l… Bill Fenner
- [xml2rfc] DTD modifications for multi-paragraph l… Elwyn Davies
- [xml2rfc] DTD modifications for multi-paragraph l… Bill Fenner