MSGID: 2:221/1.58@fidonet 27dc8051
REPLY: 1:154/10 69513d2a
PID: OpenXP/5.0.64 (Win32)
CHRS: ASCII 1
TZUTC: -0500
Hello Nick!

** On Sunday 28.12.25 - 08:11, you wrote:

 NB> If you're still referring to OpenXP here, I'm not sure if
 NB> there has been any more development lately or not (or if
 NB> there ever will be), but last time I checked, the Linux
 NB> version still didn't support utf-8.

The latest one seems to be Feb 2025:

https://sourceforge.net/projects/openxp5/files/OpenXP%205.0/


 NB> Winpoint did a little bit better, but still wasn't 100%,
 NB> and well, it's Windows only, so that's already a huge
 NB> limitation.

It thought Win-anything was going to be my final approach to  
this messaging hobby, but I actually grew quite fond of the  
text-based OpenXP.


 NB> I had mentioned a bug in how it handles time and UTC
 NB> offsets upwards of 1-2 (or more, time flies these days)
 NB> years ago, got a reply that it would be looked into, and
 NB> nothing ever came of it.

I recall something re a time issue.  But was there an  
acknowledgement? ..or just an excuse?

What's the big deal with UTF-8 in FTN anyway?  Do we need utf-8  
emojiis in these messages?

As-is, my font [Lucinda console] & charset supports French,  
Spanish, Norwegian, and few others.
-- 
  ../|ug

--- OpenXP 5.0.64
 * Origin:  (2:221/1.58)
SEEN-BY: 1/19 100 16/0 19/37 105/81 106/201 123/130 128/187 129/14
SEEN-BY: 142/104 153/7715 154/110 203/0 218/700 221/1 6 226/30 227/114
SEEN-BY: 229/110 112 134 206 300 317 400 426 428 470 664 700 705 240/5832
SEEN-BY: 266/512 280/464 5003 5006 291/111 301/1 320/119 219 319 2119
SEEN-BY: 322/757 762 342/200 396/45 423/81 460/58 633/280 712/848
SEEN-BY: 902/26 5075/35
PATH: 221/1 320/219 229/426