MSGID: 1:154/10 65d7db50   
   REPLY: 2:341/234.99 65d4d9be   
   PID: Smapinntpd/Linux 2.0 b20240216   
   CHRS: UTF-8 4   
   TZUTC: -0600   
   TID: hpt/lnx 1.9 2024-02-05   
   On Tue, 20 Feb 2024 23:56:32 +0100, Carlos Navarro -> Benny Pedersen wrote:   
      
    CN> 08/02/2024 6:08, Benny Pedersen -> Carlos Navarro:   
      
     CN>>> I've found that this issue can be fixed by adding "-keepsoftcr" to the   
     CN>>> corresponding line in jamnntpd.xlat, just like with CP866:   
      
     CN>>> ================================   
     CN>>> read UTF-8   utf-8   -keepsoftcr   
     CN>>> ================================   
      
     BP>> problem with jamnntpd is that it does not support multibyte, so only   
   can   
     BP>> change singlebyte in diffrent charsets   
      
    CN> I don't understand what you mean. JamNNTPd seems to work fine with UTF-8,   
    CN> except for some issues with quotes.   
      
   Bringing the thread from the Golded echo about Jamnntpd over here. Here's a   
   test to see if those characters are before level 2 and 3 quotes on this reply.   
      
   Regards,   
   Nick   
      
   ... "Take my advice, I don't use it anyway."   
   --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb   
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)   
   SEEN-BY: 15/0 90/1 103/705 105/81 106/201 120/616 123/10 124/5016   
   SEEN-BY: 128/260 135/225 153/757 7715 154/10 30 40 50 700 203/0 218/700   
   SEEN-BY: 220/90 221/0 6 226/18 30 227/114 229/110 112 113 206 307   
   SEEN-BY: 229/317 426 428 470 664 700 240/1120 5832 266/512 280/464   
   SEEN-BY: 280/5003 5555 282/1038 291/111 292/8125 301/1 310/31 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 770/1 2320/105 3634/12 5020/400 5054/30   
   PATH: 154/10 280/464 460/58 229/426