>From [EMAIL PROTECTED] Fri Jul 23 15: 06:15 2004
Return-Path: <[EMAIL PROTECTED]>
Received: from noxmail.sandelman.ottawa.on.ca (nox.sandelman.ottawa.on.ca
[205.150.200.181])
by lox.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id i6NJ4Jp01025
(using TLSv1/SSLv3 with cipher
I would like to propose the string "\r\n\r\x1A", so that:
- correct byte order, correct ftp transfer ==> "\r\n\r\x1A"
- correct byte order, wrong ftp UNIX to Win ==> "\r\n\n\r\"
- correct byte order, wrong ftp Win to UNIX ==> "\n\r\x1A\?"
- changed byte order, correct ftp transfer ==> "\x1A\r\n\
On Jul 23, 2004, at 11:57 AM, Gianluca Varenni wrote:
If the file is transfered from win to unix in ASCII mode, the file
should
become
\n\n\r .. In this case we recognize the first three characters
"\n\n\r", try to convert the first 12 bytes from unix-ascii to
win-ascii,
and check the by
- Original Message -
From: "Guy Harris" <[EMAIL PROTECTED]>
To: "Gianluca Varenni" <[EMAIL PROTECTED]>
Cc: "Loris Degioanni" <[EMAIL PROTECTED]>; "Fulvio Risso"
<[EMAIL PROTECTED]>; "Michael Richardson" <[EMAIL PROTECTED]>
Sent: Friday, July 23, 2004 12:14 PM
Subject: Re: new file format
- Original Message -
From: "Fulvio Risso" <[EMAIL PROTECTED]>
To: "Gianluca Varenni" <[EMAIL PROTECTED]>; "Guy Harris"
<[EMAIL PROTECTED]>
Cc: "Loris Degioanni" <[EMAIL PROTECTED]>; "Michael Richardson"
<[EMAIL PROTECTED]>
Sent: Friday, July 23, 2004 11:22 PM
Subject: RE: new file format