In article <01RQYDVJUD5A005PTU(_at_)mauve(_dot_)mrochek(_dot_)com> you write:
On 10/16/2020 4:01 PM, Ned Freed wrote:
In messages that are not Internationalized [RFC6532], emoji and any
other non-ASCII characters MUST be encoded using [MIME-Enc].
However, I just got an offlist suggestion I'd like to get reactions to:
... consider allowing the emoji to be specified (one option) as "U+1F44D",
In-Reply-React: U+1F44D U+1F622
My thought is "no". It's not that encoded-words are great, it's that they enjoy
universal deployment. Use encoded-words and access to the unencoded form is one
routine call away, if that. Anything else is more work, and no matter how much
better is looks to coding geeks, it's still nonsense to users.
I agree. Every MUA that can display Unicode already has code to handle
encoded-words. Use it. Indeed, having tracked down some MIME bugs in
mail processing libraries I can say that in many cases it would take
extra special case coding to make an MUA *not* do encoded-word
decoding on a new header field.
ietf-822 mailing list