Re: [AVT] RE: Comments on draft-ietf-avt-mime-h224-02.txt

I produce XML2RFC documents with the web tool on a PC, and normally 
check them afterward with a hex editor to make sure line and page ends 
are set up correctly.  I failed to do so with 2833bis-09 because XML2RFC 
release notes said they had fixed the tool to provide for Windows 
line-end conventions.  I see now I was mistaken: the document begins as 
usual in the past with a series of LF (x'0a') rather than CR-LF 
(x'0d0a') as required by IETF formatting conventions.  Similarly the end 
of page is marked by LF-FF-LF (x'0a0c0a'), an improvement in ordering 
over previous versions, but lacking the CRs.

When I look at draft-ietf-avt-mime-h224-02.txt, I'm surprised to see no 
form feed characters at all!  There's just a pair of LF characters at 
the end of the page.

I'm copying Marshall Rose on this note.  The problem may be intractable, 
but the ideal output of the tool (according to RFC 2234) would be:

CR-LF for line ends
CR-LF-FF-CR-LF between pages

Even, Roni wrote:
> Magnus,
> Thanks for going over the document.
> In line 
> Roni
> 
> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com] 
> Sent: Monday, June 27, 2005 3:43 PM
> To: Even, Roni; IETF AVT WG
> Subject: Comments on draft-ietf-avt-mime-h224-02.txt
> 
> Hi Roni,
> 
> I have some comments on the draft:
> 
> 1. First, it is quite irritating that the draft lacks the correct page
> break markers.
> 
> Roni: I am using xmk2rfc so it is a bit strange, can you show me an
> example.
> 
...

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt