- From: Florent Georges <fgeorges@gmail.com>
- Date: Tue, 14 Apr 2009 16:24:28 +0200
- To: Norman Walsh <ndw@nwalsh.com>
- Cc: XProc Dev <xproc-dev@w3.org>
2009/4/14 Norman Walsh wrote: > Norman Walsh <ndw@nwalsh.com> writes: >> I'm fixing the same bugs in fixed-alternative and http-request-006 now :-) > I think I've fixed http-request-006 now. The CR/LF pair that precedes > the separator is, by my reading of the RFC, part of the separator. > There's also some confusion (in my mind) about how to handle the > text->XML conversion of CR/LF pairs. I think you can have everything you want (except the boundary) in the content of one part. But for header lines, and for boundaries, when the RFC speaks about a line, or a blank line, you have to use CR/LF as line delimiter (not only LF.) But to enable interoperability, I wonder if one has to translate LF <-> CR/LF on Unices for textual media types. But my point was that at very least, the end of line for headers and boundaries must be CR/LF (and were only LF.) Seems fixed now. Regards, -- Florent Georges http://www.fgeorges.org/
Received on Tuesday, 14 April 2009 14:25:09 UTC