TZUTC: -0500
MSGID: 344.tuxpower@1:154/700 2c57e508
REPLY: 2:221/1.58@fidonet 1f2b485e
PID: Synchronet 3.21a-Linux master/e2e350d1d Apr 04 2025 GCC 14.2.1
TID: SBBSecho 3.24-Linux master/e2e350d1d Apr 04 2025 GCC 14.2.1
BBSID: PHARCYDE
CHRS: UTF-8 4
NOTE: slrn/pre1.0.4-9 (Linux)
Hey August!

On Sun, Apr 06 2025 10:35:00 -0500, you wrote:

 > I don't there is UTF-8 support on the incoming.  OpenXP is a  
 > terminal/console program afterall.

I'm currently using slrn (a linux console newsreader) that displays UTF-8 just
fine, just as well as most other console based Linux applications I use here,
so I don't think this is really an excuse/reason. Maybe moreso for Windows,
though.

 > I just tried the dove-tech-talk echo, and the TLDR material  
 > with OpenXP looks messy with unresolved conversions.  So, not  
 > sure what you consider is "handles very nicely".

Either something on your end must not be configured correctly for this. You
have to enable UTF-8 and there might have even been some mime decoding options
in the only place OpenXP has these settings (I don't remember exactly). You'll
see what I mean when you have it configured right. Or, it could be Windows
specific where it doesn't work as well.

It's also possible I set this up more precisely on Linux, and maybe didn't get
this far in regards to setup on Windows.. after realizing the Windows command
prompt doesn't work anything like a Linux console in regards to UTF-8. After
fiddling with Windows' code page 65001 for about 30 minutes, I gave up on it
and downloaded/installed it on Linux to see if I could get further.

However, I did just find this:

https://github.com/microsoft/terminal

 > Oh.. so yes.. the plaintext is what OpenXP does well.

I'd have to agree with you there. At least the ascii part of it. I don't even
think I spent much time checking on CP437 as I probably assumed it just
worked, but I'm guessing that works OK?

 > I doubt that OpenXP can ever support UTF-8 like in gui-type  
 > windows.  The limitation is the charset/font support in Windows  
 > DOS terminal.  I currently use Lucinda TT console.  It has  
 > limits to what foreign chars it supports. German, French,  
 > Italian, Spanish chars are supported.

Sure it can. At least on Linux. Windows console may need a bit more work, but
that's way above my pay grade.

You could try using 'chcp 65001' to change to whatever MS considers it's UTF-8
console support.

 > AFIK, OpenXP maintains UTF-8 chars on the outbound in NNTP-type  
 > areas.  Not sure if it renders as expected on the inbound.

I didn't try sending anything off, however on display it was all question
marks. I questioned it even more when I got Dovenet's Tech Talk area to
display properly (minus html and also mime decoded - as good as my console
newsreaders handle it) with UTF-8 characters and glyphs.

 > I *did* kinda kickstart a push to have some problems corrected.

There may be one left to push! :)

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- SBBSecho 3.24-Linux
 * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
SEEN-BY: 50/22 103/705 104/119 105/81 106/201 120/616 124/5016 128/187
SEEN-BY: 153/757 7001 7715 154/10 30 50 110 700 203/0 218/700 220/20
SEEN-BY: 220/90 221/0 6 226/18 30 44 227/114 229/110 114 206 300 317
SEEN-BY: 229/400 426 428 470 664 700 705 240/1120 5832 266/512 280/464
SEEN-BY: 280/5003 291/111 292/8125 301/1 310/31 320/219 322/757 341/66
SEEN-BY: 341/234 342/200 396/45 460/16 58 256 1124 5858 467/888 633/280
SEEN-BY: 712/848 770/1 902/26 2320/105 3634/12 5020/400 8912 5054/30
SEEN-BY: 5075/35
PATH: 154/700 10 280/464 460/58 229/426