REPLY: 1:154/10 65e3f494
MSGID: 1:153/7001 65e3f65e
CHRS: UTF-8 4
Hey Nicholas!

 NB> As far as I can tell, all looks good. I just don't know how this
 NB> type of FTN software will send it back to you. :)

It looks good here.  If it added a "Re: ", like some so-called FTN software
does, then it would have stripped bytes from the rightmost which in this case
is wrong since the rightmost is the beginning not the end.  I believe the "Re:
" thingy is a QWK standard and not really a FTN standard that I am aware of. 
I could be wrong about this but I don't believe so.

Bottomline is your software can properly handle utf-8 codes no matter where
(msg_header in this case) or the msg_body.  You have my seal of approval ...
for what it's worth.  :-)

Life is good,
Maurice

-o   -o   -o    o-  -o   -o    o-  -o    o-   o-   o-   o-   o-   o-   o-   o-
 (\   (\   (\  /)    (\   (\  /)    (\  /)   /)   /)   /)   /)   /)   /)   /)
 ^^   ^^   ^^  ^^    ^^   ^^  ^^    ^^  ^^   ^^   ^^   ^^   ^^   ^^   ^^   ^^
... Wea bið wundrum clibbor. Wolcnu scriðað.
    Sorrow is strangely clinging. Clouds glide on.
--- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
 * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 120/616 123/10 124/5016
SEEN-BY: 128/260 135/225 153/757 7001 7715 154/10 30 40 50 700 203/0
SEEN-BY: 214/22 218/0 1 601 700 820 840 850 860 870 880 930 940 220/90
SEEN-BY: 221/0 6 226/18 30 70 227/114 229/110 112 113 206 307 317
SEEN-BY: 229/400 426 428 470 664 700 240/1120 5832 266/512 280/464
SEEN-BY: 280/5003 282/1038 291/111 292/8125 301/1 310/31 320/219 322/757
SEEN-BY: 341/66 234 342/200 396/45 460/58 467/888 633/280 712/848
SEEN-BY: 770/1 2320/105 3634/12 5020/400 5075/35
PATH: 153/7001 154/10 280/464 103/705 218/700 229/426