TID: FMail-W32 2.3.0.1-B20240319
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 4
MSGID: 2:280/5555 67b9d037
REPLY: 2:5020/12000 4f5391a7
Hello Sergey,

On Friday February 21 2025 03:30, you wrote to me:

 SD> can you please, if you mark your message as "UTF-8", post erroneus
 SD> string in safe way, e.g. as hex dump, or replacing invalid codepoints
 SD> with some character like question mark? If you copy from nodelist
 SD> INVALID string with BINARY AS IS, it obviously makes your message
 SD> invalid too. I was to forcibly mark your message as CP437 to read it,
 SD> becouse trying to decode it as UTF-8 ends with error.

Hmm.. I see your point.

The program I wrote many years ago only detects the first appearance of a non
valid utf8 sequence in a line. It ignores any other invalid sequences in the
same line. So only the first occurence is replaced by a question mark, the
rest is copied as is.

I think I have found a work around.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
 * Origin: Nieuw Schnøørd (2:280/5555)
SEEN-BY: 4/0 90/0 105/81 106/201 128/187 153/7715 154/10 110 203/0
SEEN-BY: 218/700 221/6 226/30 227/114 229/110 114 317 426 428 470
SEEN-BY: 229/700 705 240/5832 280/464 5555 291/111 292/789 301/1 310/31
SEEN-BY: 320/219 341/66 234 460/58 900/0 902/0 26 905/0 5019/40 5020/1042
SEEN-BY: 5075/35
PATH: 280/5555 341/66 902/26 229/426