Re: [Tools-discuss] double new lines in drafts sent via e-mail

"Alex Rousskov" <rousskov@measurement-factory.com> writes:

> I am not sure why extra line breaks appear in the case quoted
> below. Using  Pine, I have never had that problem with
> attachments. Perhaps others know  what is going on here. This is
> something we may want to check for the  email interface of the ID
> submission tool...

Messages from john.loughney@nokia.com seem to be generated with
Microsoft Exchange V6.0.6603.0.  If they are stored in DOS format
locally, the DOS newlines are probably encoded by the client *if* the
draft is sent in base64 rather than quoted-printable (or with no
protection).

At this point, draft-savola-ipr-lastcall-04.txt is a deletion notice,
so it's difficult to see what was going on.  I don't have a message
with an attachment from John Loughney, either.

I think making the submission tool convert any newlines (\n, \r\n, \r,
and \n\r) into \n would not be a bad idea.  This applies equally to
web and email submissions.  (In fact, it might even be more important
for web submissions, as unprotected email takes care of canonicalizing
new lines -- except when sent through base64.)

Conceptually,

#include <stdio.h>

enum state_enum {NORM, N, R, RN};
typedef enum state_enum state_t;

#define NORMAL	do { 				\
			state = NORM;		\
			putchar('\n');		\
		} while (0)

int
main()
{
	int c;			/* Current character. */
	state_t state;

	state = NORM;
	while ((c = getchar()) != EOF)
		switch (state) {
		case NORM:
			if (c == '\n') state = N;
			else if (c == '\r') state = R;
			else putchar(c);
			break;
		case N:
			NORMAL;
			if (c != '\r') putchar(c);
			break;
		case R:
			NORMAL;
			if (c != '\n') putchar(c);
			break;
		}
	if (state != NORM) NORMAL;
	exit(0);
}

-- 
Stanislav Shalunov		http://www.internet2.edu/~shalunov/

Just my 0.086g of Ag.

_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/tools-discuss