Tim Legant <[EMAIL PROTECTED]> writes: >> I think this will work. Do you think the default templates should >> append .US-ASCII to From and Subject to indicate the default >> charset?
[...] > So yes, I think we gain some good documentation by so marking the > default template and there is no downside. The only downside is a strange looking header syntax in the templates. 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. 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. Of course, I will need to write up a comprehensive Template HOWTO to explain all these things, because the issue of I18N is too darned difficult to rely on implicit documentation only. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
