Subj : Test Reply To : deon From : Accession Date : Mon Dec 25 2023 08:30 am Hello deon, On Mon, 25 Dec 2023 18:17:10 +1100, you wrote: >> However (and this might be a better choice), If you don't want to >> mess with translations, that's totally fine too. But I would keep the >> CP437 CHRS kludge on your message no matter what then, and not >> use/copy the charset of the original poster. d> My goal is it keep the original message - so if multiple people are d> testing, or if somebody is sending out multiple tests - the reply lets d> you know which ones were responded to (and which werent). And if there d> were non-CP437 chars in there, you would still see them in the reply. d> My original rational for keeping the original kludge, is to honor the d> original format of the message (eg: if it is UTF-8 with UTF-8 chars, d> then keep it UTF-8, so those UTF-8 chars were preserved). The graphical d> text that the bot replies with is less important than knowing your test d> is getting out there. Ah ok. I see where you're going with this then. d> Perhaps I'll not include any high ASCII if the original message isnt d> CP437 - doesnt look like there is an obvious silver bullet. Anyway, I'll d> have a play around with options... Heck, if you do feel like tinkering around a bit, see if you can use iconv to convert the header (as a text file) to whatever charset the original poster went with then just prior to posting the reply. d> Thanks for all the feedback and ideas... No problem. However, I'll apologize in advance that I'm putting more stuff on your plate that you may or may not have thought of, because really.. it's kinda useless and cosmetic only. Had I not quoted your header back to you (which I usually don't since I'm hardwired here to export with UTF-8 - as in I force it) we wouldn't even be having this conversation. ;) Regards, Nick .... "Take my advice, I don't use it anyway." --- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32) * Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0) .