Subject: [xml2rfc] Tcl 8.4
From: [email-masked] (Marshall Rose)
Date: Fri, 21 Mar 2003 15:01:21 -0800

> I've just received this bug report:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=185793
> 
> There's a patch in it; you might want to apply it.

thanks!
    
/mtr

From: [email-masked] (Florian Weimer)
Date: Fri, 21 Mar 2003 23:38:43 +0100
Subject: [xml2rfc] Tcl 8.4
Message-ID: <[email-masked]>

Hi,

I've just received this bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=185793

There's a patch in it; you might want to apply it.

Thanks,
-- 
Florian Weimer 	                  [email-masked]
University of Stuttgart           http://CERT.Uni-Stuttgart.DE/people/fw/
RUS-CERT                          fax +49-711-685-5898

From: [email-masked] (Marshall Rose)
Date: Tue, 18 Mar 2003 10:54:14 -0800
Subject: [xml2rfc] xml2rfc-es: A spanish version
In-Reply-To: <[email-masked]>
References: <[email-masked]>
Message-ID: <[email-masked]>

> We at RFC-ES have found this tool a valuable one for our job -we plan to use 
> it to translate other RFC- and we want to ask for permision to make the 
> modified xml2rfc Tcl script (we call it 'xml2rfc-es.tcl') avalaible from our 
> website at http://www.rfc-es.org. If this is not possible, please, consider 
> the possibility of making it avalaible from the xml2rfc website.

hi. please go ahead and post your updated version of xml2rfc.tcl on your
website. in the future, i may be able to make an internationalized version of
the script that lets an author specify which language strings should be used for
the boilerplate.

thanks!

/mtr

From: [email-masked] (Pedro J. Ponce de =?iso-8859-1?q?Le=F3n?=)
Date: Tue, 18 Mar 2003 17:30:02 +0100
Subject: [xml2rfc] xml2rfc-es: A spanish version
Message-ID: <[email-masked]>

Hello,

I coordinate the RFC-to-Spanish translation group (RFC-ES) and I just 
translated to spanish the RFC2629 you wrote. I actually translated the XML 
source of the document, to be able to generate the final translation using 
xml2rfc. In order to produce a complete translation, I translated to spanish 
some strings in the xml2rfc Tcl script (The Copyright statment and a few 
other ones).

We at RFC-ES have found this tool a valuable one for our job -we plan to use 
it to translate other RFC- and we want to ask for permision to make the 
modified xml2rfc Tcl script (we call it 'xml2rfc-es.tcl') avalaible from our 
website at http://www.rfc-es.org. If this is not possible, please, consider 
the possibility of making it avalaible from the xml2rfc website.

Yours faithfully,

-------------------------------------------
Pedro J. Ponce de León Amador
Dpto. de lenguajes y sistemas informáticos
Universidad de Alicante - E03080 Spain
Tlf: +34 965 903400, ext. 2981
-------------------------------------------

PD: Please, visit www.rfc-es.org to get an idea of what is this all about.

From: [email-masked] (Julian Reschke)
Date: Sun, 16 Mar 2003 21:02:00 +0100
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
Message-ID: <[email-masked]>

> -----Original Message-----
> From: [email-masked]
> [mailto:[email-masked]]On Behalf Of Marshall Rose
> Sent: Sunday, March 16, 2003 8:26 PM
> To: Julian Reschke
> Cc: [email-masked]
> Subject: Re: [xml2rfc] Patch to support HTML spans in xml2rfc
>
>
> > My *recommendation* is not to do it at all :-)
> >
> > If you really want it in, I'd recommended to just re-use
> existing element
> > names from HTML or DocBook:
> >
> > http://www.w3.org/TR/html401/struct/text.html#h-9.2
>
> julian - humor me in the sense that people ask for a feature like
> this quite a
> lot.
>
> i don't mind adding it because one can also do things like
> *emphasis* in ascii.
>
> what i do mind is using the name of an element from html, e.g.,  <span/>,
because
> it will confuse a lot of people.

Yes,

that's why I recommend not to use "span", but things like "quote", "code",
"kbd" and "em".

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

From: [email-masked] (Marshall Rose)
Date: Sun, 16 Mar 2003 11:26:00 -0800
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
References: <[email-masked]> <[email-masked]>
Message-ID: <[email-masked]>

> My *recommendation* is not to do it at all :-)
> 
> If you really want it in, I'd recommended to just re-use existing element
> names from HTML or DocBook:
> 
> http://www.w3.org/TR/html401/struct/text.html#h-9.2

julian - humor me in the sense that people ask for a feature like this quite a
lot.

i don't mind adding it because one can also do things like *emphasis* in ascii.

what i do mind is using the name of an element from html, e.g., <span/>, because
it will confuse a lot of people.

/mtr

From: [email-masked] (Julian Reschke)
Date: Sun, 16 Mar 2003 11:40:31 +0100
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
Message-ID: <[email-masked]>

My *recommendation* is not to do it at all :-)

If you really want it in, I'd recommended to just re-use existing element
names from HTML or DocBook:

http://www.w3.org/TR/html401/struct/text.html#h-9.2

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

> -----Original Message-----
> From: [email-masked]
> [mailto:[email-masked]]On Behalf Of Marshall Rose
> Sent: Sunday, March 16, 2003 12:47 AM
> To: [email-masked]
> Cc: [email-masked]
> Subject: Re: [xml2rfc] Patch to support HTML spans in xml2rfc
>
>
> > > The point being: the purpose of RFC2629-XML-formatted
> documents is to have
> > > something, from which IETF documents can be generated easily.
> The normative
> > > versions of these documents are plain ASCII, so if your
> document requires
> > > text styles to be readable, there's a problem.
> > >
> > > *If* you add formatting, please concentrate on non-visual clues like
> > > "emphasized", "code" and "quotation" rather than font styles.
> >
> > julian is right here. there is a fairly developed set of
> conventions for the
> > ascii-enabled to *emphasize* things or "quote" them, etc. the
> trick is to use
> > non-visual terms that can be implemented across all three
> output engines.
>
> so, julian, what do you suggest we use as the name for the element?
> /mtr
> _______________________________________________
> xml2rfc mailing list
> [email-masked]
> http://lists.xml.resource.org/mailman/listinfo/xml2rfc
>

From: [email-masked] (Marshall Rose)
Date: Sat, 15 Mar 2003 15:46:33 -0800
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
References: <[email-masked]> <[email-masked]> <[email-masked]>
Message-ID: <[email-masked]>

> > The point being: the purpose of RFC2629-XML-formatted documents is to have
> > something, from which IETF documents can be generated easily. The normative
> > versions of these documents are plain ASCII, so if your document requires
> > text styles to be readable, there's a problem.
> > 
> > *If* you add formatting, please concentrate on non-visual clues like
> > "emphasized", "code" and "quotation" rather than font styles.
> 
> julian is right here. there is a fairly developed set of conventions for the
> ascii-enabled to *emphasize* things or "quote" them, etc. the trick is to use
> non-visual terms that can be implemented across all three output engines.

so, julian, what do you suggest we use as the name for the element?
/mtr

From: [email-masked] (Marshall Rose)
Date: Thu, 13 Mar 2003 07:05:26 -0800
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
References: <[email-masked]> <[email-masked]>
Message-ID: <[email-masked]>

> The point being: the purpose of RFC2629-XML-formatted documents is to have
> something, from which IETF documents can be generated easily. The normative
> versions of these documents are plain ASCII, so if your document requires
> text styles to be readable, there's a problem.
> 
> *If* you add formatting, please concentrate on non-visual clues like
> "emphasized", "code" and "quotation" rather than font styles.

julian is right here. there is a fairly developed set of conventions for the
ascii-enabled to *emphasize* things or "quote" them, etc. the trick is to use
non-visual terms that can be implemented across all three output engines.

/mtr

From: [email-masked] (Julian Reschke)
Date: Thu, 13 Mar 2003 10:59:30 +0100
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
Message-ID: <[email-masked]>

The point being: the purpose of RFC2629-XML-formatted documents is to have
something, from which IETF documents can be generated easily. The normative
versions of these documents are plain ASCII, so if your document requires
text styles to be readable, there's a problem.

*If* you add formatting, please concentrate on non-visual clues like
"emphasized", "code" and "quotation" rather than font styles.

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

> -----Original Message-----
> From: [email-masked]
> [mailto:[email-masked]]On Behalf Of Pekka Nikander
> Sent: Thursday, March 13, 2003 10:44 AM
> To: Julian Reschke
> Cc: Marshall Rose; [email-masked]
> Subject: Re: [xml2rfc] Patch to support HTML spans in xml2rfc
>
>
> Julian Reschke wrote:
> > How does this extension fit into the goals of RFC2629? How are
> you going to
> > generate ASCII/nroff from this information?
>
> I guess not ASCII.  And it should not matter for ASCII,
> since it is more a matter of readability than conveying
> information.  IMHO, there is value in having more readable
> HTML versions than ASCII versions.
>
> What comes to nroff, my command of nroff does not help
> here much.  It's been over 15 years since I last used nroff,
> and even then I didn't use much.  However, if I remember
> correctly, it is possible to have various styles, emphasis
> etc, in nroff.
>
> --Pekka
>
> _______________________________________________
> xml2rfc mailing list
> [email-masked]
> http://lists.xml.resource.org/mailman/listinfo/xml2rfc
>

From: [email-masked] (Pekka Nikander)
Date: Thu, 13 Mar 2003 11:43:43 +0200
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
References: <[email-masked]>
Message-ID: <[email-masked]>

Julian Reschke wrote:
> How does this extension fit into the goals of RFC2629? How are you going to
> generate ASCII/nroff from this information?

I guess not ASCII.  And it should not matter for ASCII,
since it is more a matter of readability than conveying
information.  IMHO, there is value in having more readable
HTML versions than ASCII versions.

What comes to nroff, my command of nroff does not help
here much.  It's been over 15 years since I last used nroff,
and even then I didn't use much.  However, if I remember
correctly, it is possible to have various styles, emphasis
etc, in nroff.

--Pekka

From: [email-masked] (Julian Reschke)
Date: Thu, 13 Mar 2003 10:39:14 +0100
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
Message-ID: <[email-masked]>

How does this extension fit into the goals of RFC2629? How are you going to
generate ASCII/nroff from this information?

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

> -----Original Message-----
> From: [email-masked]
> [mailto:[email-masked]]On Behalf Of Florian Weimer
> Sent: Thursday, March 13, 2003 10:21 AM
> To: Pekka Nikander
> Cc: Marshall Rose; [email-masked]
> Subject: Re: [xml2rfc] Patch to support HTML spans in xml2rfc
>
>
> Pekka Nikander <[email-masked]> writes:
>
> > One thing I thought about was <c/> or <cs/>, as for Character Style,
> > but went with <span/> because it was more logical to me :-)
>
> <c/> appears to be quite reasonable.  Your intent is to typeset this
> in typewriter style, isn't it? <c/> reminds me of <code/>...
>
> --
> Florian Weimer 	                  [email-masked]
> University of Stuttgart           http://CERT.Uni-Stuttgart.DE/people/fw/
> RUS-CERT                          fax +49-711-685-5898
> _______________________________________________
> xml2rfc mailing list
> [email-masked]
> http://lists.xml.resource.org/mailman/listinfo/xml2rfc
>

From: [email-masked] (Pekka Nikander)
Date: Thu, 13 Mar 2003 11:25:08 +0200
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
References: <[email-masked]>	<[email-masked]>	<[email-masked]> <[email-masked]>
Message-ID: <[email-masked]>

Florian Weimer wrote:
>
> <c/> appears to be quite reasonable.  Your intent is to typeset this
> in typewriter style, isn't it? <c/> reminds me of <code/>...

Actually my intend is to support any HTML span styles,
the default being italic/emphasized.

The code converts the XML <whatever>foo</whatever>
into HTML <span class="emph">foo</span>, and the
intention is to convert XML <whatever style="bar">foo</whatever>
into HTML <span class="bar">foo</span>.  However,
I don't know if I implemented right the latter.

--Pekka

From: [email-masked] (Florian Weimer)
Date: Thu, 13 Mar 2003 10:21:20 +0100
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]> (Pekka Nikander's message of "Thu, 13 Mar 2003 06:44:55 +0200")
References: <[email-masked]> <[email-masked]> <[email-masked]>
Message-ID: <[email-masked]>

Pekka Nikander <[email-masked]> writes:

> One thing I thought about was <c/> or <cs/>, as for Character Style,
> but went with <span/> because it was more logical to me :-)

<c/> appears to be quite reasonable.  Your intent is to typeset this
in typewriter style, isn't it? <c/> reminds me of <code/>...

-- 
Florian Weimer 	                  [email-masked]
University of Stuttgart           http://CERT.Uni-Stuttgart.DE/people/fw/
RUS-CERT                          fax +49-711-685-5898

From: [email-masked] (Pekka Nikander)
Date: Thu, 13 Mar 2003 06:49:46 +0200
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
References: <[email-masked]>	<[email-masked]> <[email-masked]>
Message-ID: <[email-masked]>

Henrik Levkowetz wrote:
> On Wed, 12 Mar 2003 12:29:56 -0800, Marshall Rose <[email-masked]> wrote:
> 
>>- i would really like to avoid using an html-specific term as the name
>>  of the element, i.e., i would prefer to replace <span/> with something
>>  else. suggestions anyone?
> 
> 
> <box />  ?

No.  Boxes may be high.   And they are rectangular, while
a span/whatever may be irregular if it spans (no pun intended)
multiple lines.

--Pekka

From: [email-masked] (Pekka Nikander)
Date: Thu, 13 Mar 2003 06:46:48 +0200
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
References: <[email-masked]>	<[email-masked]> <[email-masked]>
Message-ID: <[email-masked]>

Henrik Levkowetz wrote:
> On Wed, 12 Mar 2003 12:29:56 -0800, Marshall Rose <[email-masked]> wrote:
> 
>>- i would really like to avoid using an html-specific term as the name
>>  of the element, i.e., i would prefer to replace <span/> with something
>>  else. suggestions anyone?
> 
> 
> <box />  ?

No.  Boxes may be high.   And they are rectangular, while
a span/whatever may be irregular if it spans (no pun intended)
multiple lines.

--Pekka

From: [email-masked] (Pekka Nikander)
Date: Thu, 13 Mar 2003 06:44:55 +0200
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
References: <[email-masked]> <[email-masked]>
Message-ID: <[email-masked]>

Marshall Rose wrote:
> - i think the DTD change you made isn't quite right, in that it adds
>   <emph/> and <tt/> (instead of <span/>) to the content model for <t/>.

You are right.  Sorry about that.  The fix is easy enough, though.

> - i would really like to avoid using an html-specific term as the name
>   of the element, i.e., i would prefer to replace <span/> with something
>   else. suggestions anyone?

I agree very much.  I just needed this now, and couldn't come
up with a better term.  As you can see from the mistake in the DTD,
I first had <emph/> and <tt/>, but then replaced them with <span/>.

One thing I thought about was <c/> or <cs/>, as for Character Style,
but went with <span/> because it was more logical to me :-)

> - i don't think the changes you made for the non-html output modes will
>   work the way you think given the way things get expanded, counted, and
>   written, but i can probably figure out a work around for that.

May well be.  It has been ages since I last did TCL coding (that
was around 1992, and TCL has evolved since that...).  Besides,
I didn't have that much time to study the internals of xml2rfc.

Anyway, thanks for providing the tool and framework in the first place.

--Pekka

From: [email-masked] (Henrik Levkowetz)
Date: Thu, 13 Mar 2003 02:05:30 +0100
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
References: <[email-masked]> <[email-masked]>
Message-ID: <[email-masked]>

On Wed, 12 Mar 2003 12:29:56 -0800, Marshall Rose <[email-masked]> wrote:
> - i would really like to avoid using an html-specific term as the name
>   of the element, i.e., i would prefer to replace <span/> with something
>   else. suggestions anyone?

<box />  ?

	Henrik

-- 
  Taxes are not levied for the benefit of the taxed. 

From: [email-masked] (Marshall Rose)
Date: Wed, 12 Mar 2003 12:29:56 -0800
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
In-Reply-To: <[email-masked]>
References: <[email-masked]>
Message-ID: <[email-masked]>

> Enclosed is a simple patch to xml2rfc that allows
> it to support HTML style spans, allowing one to
> have emphasized words in an HTML version of a document.

thanks very much.
    
a couple of comments:

- i think the DTD change you made isn't quite right, in that it adds
  <emph/> and <tt/> (instead of <span/>) to the content model for <t/>.
    
- i would really like to avoid using an html-specific term as the name
  of the element, i.e., i would prefer to replace <span/> with something
  else. suggestions anyone?
    
- i don't think the changes you made for the non-html output modes will
  work the way you think given the way things get expanded, counted, and
  written, but i can probably figure out a work around for that.
    
/mtr

From: [email-masked] (Pekka Nikander)
Date: Wed, 12 Mar 2003 13:45:07 +0200
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
Message-ID: <[email-masked]>

This is a multi-part message in MIME format.
--------------020100030607040304030609
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Enclosed is a simple patch to xml2rfc that allows
it to support HTML style spans, allowing one to
have emphasized words in an HTML version of a document.

<t>
     This in an <span>example.</span>
</t>

It would be easy to expand it to support other
styles, like bold or typewriter, but I didn't
need that (yet).  Furthermore, someone knowledgeable
with (x)roff might consider adding support for it.

--Pekka Nikander

--------------020100030607040304030609
Content-Type: text/plain;
 name="xml2rfc.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="xml2rfc.diff"

diff -u xml2rfc-1.17-orig/rfc2629.dtd xml2rfc-1.17/rfc2629.dtd
--- xml2rfc-1.17-orig/rfc2629.dtd	Fri Jan 31 02:43:30 2003
+++ xml2rfc-1.17/rfc2629.dtd	Wed Mar 12 13:07:59 2003
@@ -147,7 +147,11 @@
           anchor      ID                 #IMPLIED
           title       %ATEXT;            #REQUIRED>
 
-<!ELEMENT t           (%TEXT;|list|figure|xref|eref|iref|vspace)*>
+<!ELEMENT span        (%CTEXT;)>
+<!ATTLIST span
+          style       %ATEXT;            #IMPLIED>
+
+<!ELEMENT t           (%TEXT;|list|figure|xref|eref|iref|vspace|emph|tt)*>
 <!ATTLIST t
           hangText    %ATEXT;            #IMPLIED>
 
diff -u xml2rfc-1.17-orig/xml2rfc.tcl xml2rfc-1.17/xml2rfc.tcl
--- xml2rfc-1.17-orig/xml2rfc.tcl	Fri Feb 14 06:32:19 2003
+++ xml2rfc-1.17/xml2rfc.tcl	Wed Mar 12 13:09:33 2003
@@ -2832,7 +2832,7 @@
           
 set ctexts   { title organization street city region code country phone
                facsimile email uri area workgroup keyword xref eref
-               seriesInfo }
+               seriesInfo span }
 
 set categories \
              { {std  "Standards Track" STD
@@ -3140,6 +3140,8 @@
                 -
             vspace
                 -
+            span
+                -
             back {
                 if {[lsearch0 $stack references] < 0} {
                     pass2begin_$name $elemN
@@ -4432,6 +4434,18 @@
     vspace_$mode $attrs(blankLines)
 }
 
+# span element
+
+proc pass2begin_span {elemX} {
+    global counter depth elemN elem passno stack xref
+    global mode
+
+    array set attrs [list style "emph"]
+    array set attrs $elem($elemX)
+
+    span_$mode $attrs(.CTEXT) $attrs(style)
+}
+
 
 # the references/reference elements
 
@@ -5312,6 +5326,10 @@
     set eatP 1
 }
 
+proc span_txt {text style} {
+    write_text_txt "[chars_expand $text]"
+}
+
 proc references_txt {tag {title ""} {erefP 0}} {
     global counter depth elemN elem passno stack xref
     global options
@@ -5876,6 +5894,7 @@
     p.copyright { color: #000000; font-size: 10px;
                   font-family: verdana, charcoal, helvetica, arial, sans-serif }
     p { margin-left: 2em; margin-right: 2em; }
+    span.emph { font-style: italic; }
     li { margin-left: 3em;  }
     ol { margin-left: 2em; margin-right: 2em; }
     ul.text { margin-left: 2em; margin-right: 2em; }
@@ -6352,6 +6371,14 @@
     set hangP 0
 }
 
+proc span_html {text style} {
+    global options
+    global stdout
+    global doingP hangP
+
+    puts -nonewline $stdout "<span class=\"$style\">$text</span>"
+}
+
 # don't need to return anything even though txt/nr versions do...
 
 proc references_html {tag {title ""} {erefP 0}} {
@@ -7466,6 +7493,10 @@
     }
 
     set eatP 1
+}
+
+proc span_nr {text style} {
+    write_text_nr "[chars_expand $text]"
 }
 
 proc references_nr {tag {title ""} {erefP 0}} {
Only in xml2rfc-1.17: xml2rfc.tcl~

--------------020100030607040304030609--

From: [email-masked] (Pekka Nikander)
Date: Wed, 12 Mar 2003 13:13:08 +0200
Subject: [xml2rfc] Patch to support HTML spans in xml2rfc
Message-ID: <[email-masked]>

This is a multi-part message in MIME format.
--------------080508030009020300010603
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Enclosed is a simple patch to xml2rfc that allows
it to support HTML style spans, allowing one to
have emphasized words in an HTML version of a document.

<t>
    This in an <span>example.</span>
</t>

It would be easy to expand it to support other
styles, like bold or typewriter, but I didn't
need that (yet).  Furthermore, someone knowledgeable
with (x)roff might consider adding support for it.

--Pekka Nikander

--------------080508030009020300010603
Content-Type: text/plain;
 name="xml2rfc.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="xml2rfc.diff"

diff -u xml2rfc-1.17-orig/rfc2629.dtd xml2rfc-1.17/rfc2629.dtd
--- xml2rfc-1.17-orig/rfc2629.dtd	Fri Jan 31 02:43:30 2003
+++ xml2rfc-1.17/rfc2629.dtd	Wed Mar 12 13:07:59 2003
@@ -147,7 +147,11 @@
           anchor      ID                 #IMPLIED
           title       %ATEXT;            #REQUIRED>
 
-<!ELEMENT t           (%TEXT;|list|figure|xref|eref|iref|vspace)*>
+<!ELEMENT span        (%CTEXT;)>
+<!ATTLIST span
+          style       %ATEXT;            #IMPLIED>
+
+<!ELEMENT t           (%TEXT;|list|figure|xref|eref|iref|vspace|emph|tt)*>
 <!ATTLIST t
           hangText    %ATEXT;            #IMPLIED>
 
diff -u xml2rfc-1.17-orig/xml2rfc.tcl xml2rfc-1.17/xml2rfc.tcl
--- xml2rfc-1.17-orig/xml2rfc.tcl	Fri Feb 14 06:32:19 2003
+++ xml2rfc-1.17/xml2rfc.tcl	Wed Mar 12 13:09:33 2003
@@ -2832,7 +2832,7 @@
           
 set ctexts   { title organization street city region code country phone
                facsimile email uri area workgroup keyword xref eref
-               seriesInfo }
+               seriesInfo span }
 
 set categories \
              { {std  "Standards Track" STD
@@ -3140,6 +3140,8 @@
                 -
             vspace
                 -
+            span
+                -
             back {
                 if {[lsearch0 $stack references] < 0} {
                     pass2begin_$name $elemN
@@ -4432,6 +4434,18 @@
     vspace_$mode $attrs(blankLines)
 }
 
+# span element
+
+proc pass2begin_span {elemX} {
+    global counter depth elemN elem passno stack xref
+    global mode
+
+    array set attrs [list style "emph"]
+    array set attrs $elem($elemX)
+
+    span_$mode $attrs(.CTEXT) $attrs(style)
+}
+
 
 # the references/reference elements
 
@@ -5312,6 +5326,10 @@
     set eatP 1
 }
 
+proc span_txt {text style} {
+    write_text_txt "[chars_expand $text]"
+}
+
 proc references_txt {tag {title ""} {erefP 0}} {
     global counter depth elemN elem passno stack xref
     global options
@@ -5876,6 +5894,7 @@
     p.copyright { color: #000000; font-size: 10px;
                   font-family: verdana, charcoal, helvetica, arial, sans-serif }
     p { margin-left: 2em; margin-right: 2em; }
+    span.emph { font-style: italic; }
     li { margin-left: 3em;  }
     ol { margin-left: 2em; margin-right: 2em; }
     ul.text { margin-left: 2em; margin-right: 2em; }
@@ -6352,6 +6371,14 @@
     set hangP 0
 }
 
+proc span_html {text style} {
+    global options
+    global stdout
+    global doingP hangP
+
+    puts -nonewline $stdout "<span class=\"$style\">$text</span>"
+}
+
 # don't need to return anything even though txt/nr versions do...
 
 proc references_html {tag {title ""} {erefP 0}} {
@@ -7466,6 +7493,10 @@
     }
 
     set eatP 1
+}
+
+proc span_nr {text style} {
+    write_text_nr "[chars_expand $text]"
 }
 
 proc references_nr {tag {title ""} {erefP 0}} {
Only in xml2rfc-1.17: xml2rfc.tcl~

--------------080508030009020300010603--

From: [email-masked] (Marshall Rose)
Date: Tue, 11 Mar 2003 09:02:42 -0800
Subject: [xml2rfc] Mangled table of contents when appendix sections are placed before references
In-Reply-To: <[email-masked]>
References: <[email-masked]>
Message-ID: <[email-masked]>

> 	I tried to place 3 appendix sections in the <back> matter,
> before <references>, with the result that the table of contents
> listing these got a bit mangled (note the sequence of page numbers,
> 45, 46, 47, *42*, *43*, 47, 48):
> ...

well, the fundamental problem here is that xml2rfc doesn't validate the input
against the dtd and makes some poor assumptions as a result.

this sort of motivates me to add a cheap validator to xml2rfc... (if you use the
web-based service at http://xml.resource.org/ the cgi script runs a validator
before invoking xml2rfc.tcl)

/mtr

From: [email-masked] (Henrik Levkowetz)
Date: Tue, 11 Mar 2003 15:28:53 +0100
Subject: [xml2rfc] Mangled table of contents when appendix sections are placed before references
Message-ID: <[email-masked]>

Hi,

	I tried to place 3 appendix sections in the <back> matter,
before <references>, with the result that the table of contents
listing these got a bit mangled (note the sequence of page numbers,
45, 46, 47, *42*, *43*, 47, 48):

        Authors' Addresses . . . . . . . . . . . . . . . . . . . . .  45
   A.   Method Specific Behavior . . . . . . . . . . . . . . . . . .  46
   A.1  Message Integrity Checks . . . . . . . . . . . . . . . . . .  46
   B.   Change Log . . . . . . . . . . . . . . . . . . . . . . . . .  47
        Normative References . . . . . . . . . . . . . . . . . . . .  42
        Informative References . . . . . . . . . . . . . . . . . . .  43
   C.   Open issues  . . . . . . . . . . . . . . . . . . . . . . . .  47
        Intellectual Property and Copyright Statements . . . . . . .  48

I'm sending complete input/output files to Marshall.

	Henrik

-- 
  Tommy was a chemist 
  But now he is no more 
  For what he thought was H2O 
  Was H2SO4. 

From: [email-masked] (Julian Reschke)
Date: Sun, 9 Mar 2003 22:05:36 +0100
Subject: [xml2rfc] External entities over HTTP broken in IE and Mozilla
In-Reply-To: <[email-masked]>
Message-ID: <[email-masked]>

> From: [email-masked]
> [mailto:[email-masked]]On Behalf Of Dan Kohn
> Sent: Sunday, March 09, 2003 9:42 PM
> To: [email-masked]
> Subject: [xml2rfc] External entities over HTTP broken in IE and Mozilla
> 
> ...
> 
> Not fetching external entities over HTTP (or at all for Mozilla) seems
> to be a bug in both browsers.  Can others please let me know the
> situation for other browsers?  Anyone know the XML people at MSFT and

Are there other browser supporting XSLT?

> Netscape who might be convinced to fix this?

It's probably a matter of the security approach.

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 

From: [email-masked] (Dan Kohn)
Date: Sun, 9 Mar 2003 12:41:49 -0800
Subject: [xml2rfc] External entities over HTTP broken in IE and Mozilla
Message-ID: <[email-masked]>

I'm now using external entities for citations as described at
<http://xml.resource.org>.  However, neither IE 6 nor Mozilla 1.2.1 for
Windows are able to complete the XSLT transform for
<http://www.dankohn.com/draft-kohn-news-article-01a.xml> when it's
fetched using HTTP.  IE gives an error for the first external entity,
and Mozilla transforms the file without fetching the external entities.

IE does successfully transform the file when it opens off of disk (after
warning about fetching external entities), while Mozilla transforms the
file without fetching references whether by disk or over HTTP.

By contrast, both browsers do fine transforming
<http://www.dankohn.com/rfc2396bis.xml> when fetched over HTTP or off of
disk, because it doesn't use external entities.

Not fetching external entities over HTTP (or at all for Mozilla) seems
to be a bug in both browsers.  Can others please let me know the
situation for other browsers?  Anyone know the XML people at MSFT and
Netscape who might be convinced to fix this?

          - dan
--
Dan Kohn <mailto:[email-masked]>
<http://www.dankohn.com/>  <tel:+1-650-327-2600>