"Jason R. Mastaler" <[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?

My first inclination was no.

> The reason I'm learning towards this is that it gives a clear
> indication that the default charset is US-ASCII and alludes to the
> fact that one can change it.  

But this is a good point.

> If the .US-ASCII is left off, users may be more inclined to input the
> non-US_ASCII text without changing the charset suffix.

And so is this.  So yes, I think we gain some good documentation by so
marking the default template and there is no downside.

> > Perhaps just attempting to encode the header with that charset and
> > catching any exceptions is good enough.
> 
> Yup, a LookupError is raised if this is attempted, so I don't think we
> need to explicitly do any lookups before the encoding attempt.

Excellent.  I suspected as much, but wasn't sure.


Tim
_________________________________________________
tmda-workers mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-workers

Reply via email to