MSGID: 2:221/1.58@fidonet dff112c9   
   REPLY: 2:310/31.3@fidonet dff27005   
   PID: OpenXP/5.0.42 (Win32)   
   CHRS: ASCII 1   
   TZUTC: -0500   
   Hello Martin!   
      
   ** 31.12.19 - 09:18, Martin Foster wrote to August Abolins:   
      
    AA>> I think we had a little chat about UTF-8 before (can't remember),   
    AA>> but why is it that OXP doesn't display utf-8 chars all that well?   
      
    MF>Yes we did and the thread was started by your good self on 4th April   
    MF>2019 entitled "oxp: UTF-8". Some very interesting stuff came out of   
    MF>that thread and in particular, the developers comments which I posted   
    MF>in a message dated 5th April 2019.   
      
   Thank you for the reminder.  I reviewed those messages.   
      
   Being a DOS program, oxp's UTF-8 results are highly dependent on the Font     
   set in use and the limits of that font's support.  I thought Lucinda     
   Console font would solve all the problems, but it does not.   
      
   In other news, I am still baffled how oxp decides to use IBM437 and when     
   to use UTF-8, or even when it just uses US-ASCII for outgoing messages.   
      
   Are key chars triggering the selection?   
      
      
     ../|ug   
      
   --- OpenXP 5.0.42   
    * Origin: o,,,,o§ø`ø§o,,,,o§ø`ø§o,,,,o (2:221/1.58)   
   SEEN-BY: 1/123 90/1 154/10 203/0 221/1 6 360 227/114 229/426 1014   
   SEEN-BY: 240/5832 249/206 317 400 280/464 5003 292/854 310/31 317/3   
   SEEN-BY: 322/757 342/200 396/45 423/120 712/848 770/1 2452/250   
   PATH: 221/1 280/464 229/426