Re: Charset in newgroup sample

Hi Russ,

>> wouldn't it be better to put the charsets in order to highlight the
>> fact they are useful (though it is said the default is US-ASCII)?
>
> Yeah, probably a good idea.  I'll make that change.

Thanks for your commit.


>> Content-Type: multipart/mixed; boundary="nxtprt"; charset=us-ascii
>
> As near as I can tell from RFC 2046, charset is not a valid parameter for
> multipart/* content types.  It's only supposed to go on the final
> constituent parts.  Among other things, this avoids...
>
>> In our case, the most important is the second one.  Incidentally,
>> I wonder what happens when the first one is defined to utf-8 and
>> the second one is undefined.  Is it utf-8 (out of transitivity)
>> or us-ascii?
>
> ...that problem.  :)

All right!  Thanks!

-- 
Julien ÉLIE

« There's a way of transferring funds that is even faster
  than electronic banking.  It's called marriage. » (Sam Kinison)