MSGID: 2:221/360 5caa332a   
   REPLY: 2:310/31 5ca9efb3   
   PID: JamNNTPd/OS2 1.3 20190208   
   TID: GE/2 1.2   
   CHRS: UTF-8 2   
   TZUTC: 0300   
   On 07/04/2019 5:40 a.m., Richard Menedetter : August Abolins wrote:   
      
   > 06 Apr 19 17:38:50, August Abolins wrote to All:   
   >   
   >   AA> Daudz baltu dieniņu Laimiņa dodi,   
   >   AA> Diženi, raženi dzīvojoti!   
      
      
   > This time you have inserted the correct charset kludge, identifying   
   > that you used UTF-8. Hence it will show up correctly on all UTF-8   
   > capable readers. Winpoint does not support UTF-8 I think. But OpenXP   
   > oder Goated should show it.   
   TB did the correct charset kludge, outbound.   
      
   Can OpenXP use an external editor?  That might be a good solution.   
      
      
   > I hope that the answer is OK now.   
   > Giated is at a very, very early stage.   
   > So I changed the default charset for this echo to UTF-8.   
   > It should look OK now even in my answer. (I hope)   
      
   Thank you so much!  The Latvian chars look great coming back to my TB/nntp   
   reader.   
      
   The problem seems to be OpenXP does not embrace the latvian/baltic charset in   
   its codepage offering, even with UTF-8 enabled.   
      
   Would have been cool to sign off with my name in full Latvian glory:   
      
   Āboliņšš   
      
   This place is a nice summary list of chars:   
      
   https://altcodeunicode.com/alt-codes-for-latvian-letters-with-ac   
   ents-or-diacritics/   
      
   .../|ug   
      
   --- Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.   
    * Origin: - nntp://rbb.fidonet.fi - Lake Ylo - Finland - (2:221/360)   
   SEEN-BY: 15/2 19/10 123/1970 154/10 203/0 221/0 1 6 360 226/17 229/107   
   SEEN-BY: 229/354 426 1014 240/5832 249/206 317 400 280/464 5003 292/854   
   SEEN-BY: 310/31 317/3 322/757 342/200 393/68 396/45 423/120 712/848   
   SEEN-BY: 770/1 2452/250   
   PATH: 221/360 1 280/464 229/426