MSGID: 1:154/10 65db60a4   
   REPLY: 2:341/234.99 65db238c   
   PID: Smapinntpd/Linux 2.0 b20240216   
   CHRS: UTF-8 4   
   TZUTC: -0600   
   TID: hpt/lnx 1.9 2024-02-05   
   On Sun, 25 Feb 2024 18:25:08 +0100, Carlos Navarro -> Benny Pedersen wrote:   
      
    BP>> problem with jamnntpd is that it does not support multibyte,   
      
    CN> You're right about JamNNTPd not supporting multibyte. It wraps lines at   
    CN> 79 bytes, not at 79 chars. Therefore those that have UTF-8 chars (2 or   
    CN> more bytes) become shorter when wrapped. The more UTF-8 chars a line   
    CN> has, the shorter.   
      
    CN> This is noticeable in readers that don't support flowed text (most NNTP   
    CN> clients).   
      
    CN> ASCII:   
    CN> aeiou aeiou aeiou aeiou aeiou aeiou aeiou aeiou aeiou aeiou aeiou aeiou   
    CN> aeiou aeiou   
      
    CN> UTF-8:   
    CN> áéíóú áéíóú áéíóú áéíóú áéíóú áéíóú   
    CN> áéíóú áéíóú áéíóú áéíóú áéíóú áéíóú   
    CN> áéíóú áéíóú   
      
   For the record, def_flowed=off changes what looked correct before to this.   
   This can also be a test for the top quoted line to see if those pesky   
   non-breaking spaces are added here or not.   
      
   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