On 2019 Apr 04 00:52:00, you wrote to All:

 AA> I have Config/Options/MessageReader configured with UTF-8 enabled
 AA> (it's actually the default.

 AA> But UTF-8 chars don't seem to render properly.

 AA> It that a bug?

what is your OS using? that's the key... if you are on winwhatever, you may be
using CP1252 but in modern winwhatever, it could be UTF-16... the thing is that
 the old (single byte) codepages are basically out but there's still a lot of
software that tries to use them when mapping characters and rendering glyphs...
 if the character doesn't exist in the SBCP (single byte codepage), then it is
not rendered at all or maybe it is rendered as a box with an 'x' in it or
possibly as a question mark... if there's a character in that position in the
256 byte codepage, you may see the wrong glyph...

it gets really deep when entering the world of MBCS (multi byte character
sets)...

FWIW: the message i'm replying to carries a "CHRS: ASCII 1" control line...
this is perfectly fine since your post contains only 7bit ASCII characters...
if you are interested in looking further, http://ftsc.org/docs/fts-5003.001

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Frog philosophy: Time's fun when you're having flies.
---
 * Origin:  (1:3634/12.73)