TID: FMail-W32 2.2.0.0
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 4
MSGID: 2:280/5555 65e57e37
REPLY: 1:104/117 65e50984
Hello Vitaliy,

On Sunday March 03 2024 16:31, you wrote to me:

 MvdV>> Perhaps the best strategy is to have Golded alway use UTF-8
 MvdV>> internally. Almost everyone else does these days...

 VA> That would be perfect. It only takes huge amount of effort. Especially
 VA> with keeping code backward compatible with systems, which may not have
 VA> Unicode support. I keep thinking about it and looking for possible
 VA> ways to implement.

Backwards compatibility is nice but there always comes a point that it gets in
the way of progress and it has to be dropped. Are you thinking about the DOS
version? If so I say, forget about it. Freeze the DOS version, the small
minority that still uses DOS will have to make do with what they have fo the
rest of the life of DOS.

Another way may be to not use UTF-8 internally but use two byte widechrs
everywhere and simple store the raw unicode code point. Conversion to and from
code point to UTF-8 is simple. That will limit the use to the first 65535 code
points, but that might be enough for the remaining life of Fidonet. OTOH, that
is almost the same as what Window XP did. It used UTF-16 internally and
Microsoft now regrets that.

 VA> For example function, which splits message to lines is almost 1000
 VA> lines long! It has variables, used in multiple places, it not only
 VA> splits the message, but guess charset, do recoding and other fun
 VA> stuff.

Wauw!


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
 * Origin: Nieuw Schnøørd (2:280/5555)
SEEN-BY: 15/0 18/200 19/50 90/1 105/81 106/201 987 124/5014 5016 128/260
SEEN-BY: 129/305 130/330 135/225 153/7715 218/700 226/30 227/114 229/110
SEEN-BY: 229/112 113 206 307 317 400 426 428 470 664 700 266/512 280/464
SEEN-BY: 282/1038 291/111 292/854 320/219 322/757 342/200 387/21 25
SEEN-BY: 396/45 460/58 633/280 712/848
PATH: 280/5555 464 396/45 229/426