"Jason R. Mastaler" <[EMAIL PROTECTED]> writes: > I think I'll make the .CHARSET optional, defaulting to US-ASCII, so > users who aren't planning to use non-ASCII in their templates don't > have to add this suffix.
Yes. I was definitely thinking that if no encoding is specified, we won't bother encoding the field. Which means it should be US-ASCII text. If you put something other than ASCII in a header without a specified encoding, it's your problem! > I'll also make BodyEncoding optional for the same reasons. So, > US-ASCII-only users (a large chunk) won't actually have to modify > their templates at all which will be nice. Makes sense. Although, will you leave the BodyEncoding statement in the default templates, as a form of documentation? Tim _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
