Missing feature: decoding UTF-8 escape sequences

[focuspulling]

Nice plugin, in my use case, for fixing Unicode "escaped characters" such as \u00e2\u0080\u0099 from a sloppy Meta download of posts into a JSON file (decoding to a single apostrophe) however the Decode functions under the drop-down menu failed to catch/fully decode numerous "foreign" characters that resulted in, e.g., ä and ë etc. Why? Is the plugin not completely functional?

[rdipardo]

\u00e2\u0080\u0099 is the UTF-8 encoding for U+2019 Right Single Quotation Mark.

The decoding feature was originally designed for JavaScript, which uses UTF-16 (\u2019).

As of the latest version, each of the following will decode to ’ as expected:

’
’
’
\u2019
\u002019

You can also decode any UTF-32 character up to U+10FFFF.

Decoding UTF-8 has not been implemented yet. It's something I may get around to if more users request it, but it's generally out of scope for a web-page editing plugin, as browsers don't yet support UTF-8-encoded entities. For example, ’ will render as ’, not ’.

[focuspulling]

I'm more confused now.

You wrote, "Decoding UTF-8 has not been implemented yet." But I'm reading lots of reports that your plugin used to have a "Decode JS" option and isn't that the relevant operation? Altogether, do you not have any advice on finding something that does what your plugin cannot at this time?