Re: Informational RFC to be: draft-rmcgowan-unicode-procs-03.txt

[Rick McGowan <rick@unicode.org>]

Thank you for the notification.

The document was produced with XML. I submitted both text and XML. I used  
the recommended XML to text tool to produce the text file. There is an  
author address and full information in the XML, so unless the tool is  
broken, I don't understand why the resulting text document is  
unsatisfactory.

Could someone explain to me precisely what needs to be done to the XML or  
text file(s) to cause the author's address section to be inserted?

Thank you,
	Rick

---------------------------------

> From: RFC Editor <rfc-editor@rfc-editor.org>
> Date: 2003-08-19 14:30:36 -0700
> To: IESG <iesg@ietf.org>
> Subject: Informational RFC to be:
> draft-rmcgowan-unicode-procs-03.txt
> Cc: RFC Editor <rfc-editor@rfc-editor.org>, rick@unicode.org,
> iesg-secretary <iesg-secretary@ietf.org>
>
> IESG,
>
> This RFC-to-be was submitted to the RFC Editor to be published as
> Informational: draft-rmcgowan-unicode-procs-03.txt.
>
>
> Four week timeout is initiated (16 August 2003).
>
>
>   A Summary of Unicode Consortium Procedures, Policies, Stability, and
>                              Public Access
>
>    This memo describes various internal workings of the Unicode
>    Consortium for the benefit of participants in the IETF. It is
>    intended solely for informational purposes. Included are discussions
>    of how the decision-making bodies of the Consortium work and what
>    their procedures are, as well as information on public access to the
>    character encoding & standardization processes.
>
>
> ** Please note that there is not an authors address section within
>    the document.  We will request that the author insert one if/when
>    the document is to be published.  If you need to contact the
>    author, the following is the email address we have for
>    Rick McGowan:
>
>       rick@unicode.org
>
>
> Sincerely,
>
> Sandy Ginoza - USC/ISI
> Request for Comments Documents
>
>