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 guess that would be OK.
Ned