On Fri, Oct 31, 2003 at 06:44:17PM -0800, Tim Showalter wrote:
ned(_dot_)freed(_at_)mrochek(_dot_)com wrote:
I suppose the obvious thing to do would be to let the user edit the
charset field separately from the content of the field. But this
gets very complex very quickly -- there are lots and lots of charsets
and what do you do when they pick a charset that doesn't support all
the characters that were specified?
Simply allowing access to the raw encoded words in the editor is probably
what's going to happen in any case.
Do you think it's worth noting this as a SHOULD?
I don't think we should describe or limit the behavior of editor
applications at all.
One, clients aren't our core competency. We're describing a language,
not the diverse applications that produce scripts written in it.
Secondly, if we have advice to give, surely it'll be of value to e-mail
client user interfaces everywhere. It should go into a Best Practices
RFC for e-mail clients in general, not into a sieve extension's option.
Jutta