On Tue, 2005-11-29 at 10:25 -0500, Jeffrey Stedfast wrote:
Might be nitpicking, but RFC 2822 says:
The process of moving from this folded multiple-line representation
of a header field to its single line representation is called
unfolding. Unfolding is accomplished by simply
On Mon, 2005-11-28 at 12:12 -0500, Jeffrey Stedfast wrote:
I see what you are thinking, but by the time this code is run on any
input, the \r has already been stripped and you cannot, by definition,
have \n\n in a header (it terminates the header block so we don't have
to worry about that).
On Tue, 2005-11-29 at 09:55 +0100, Jules Colding wrote:
On Mon, 2005-11-28 at 12:12 -0500, Jeffrey Stedfast wrote:
I see what you are thinking, but by the time this code is run on any
input, the \r has already been stripped and you cannot, by definition,
have \n\n in a header (it terminates
On Mon, 2005-11-28 at 15:10 +0100, Jules Colding wrote:
*dst = *rfc822_header;
if (!dst)
break;
That should be:
*dst = *rfc822_header;
if ('\0' == *dst)
break;
--
jules
On Mon, 2005-11-28 at 15:10 +0100, Jules Colding wrote:
Hi,
Consider the camel_header_unfold() function:
char *
camel_header_unfold(const char *in)
{
char *out = g_malloc(strlen(in)+1);
const char *inptr = in;
char c, *o = out;
o = out;
while ((c =
