TID: FMail-lnx64 2.2.1.1
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20240209
MSGID: 2:280/464 65d868e5
REPLY: 1:154/10 65d7db50
Hi Nicholas,

On 2024-02-22 17:40:04, you wrote to Carlos Navarro:

  CN>>>> I've found that this issue can be fixed by adding "-keepsoftcr"
  CN>>>> to
  CN>>>> the 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
  BP>>> only can change singlebyte in diffrent charsets
 ^^

 CN>> I don't understand what you mean. JamNNTPd seems to work fine with
 CN>> UTF-8, except for some issues with quotes.

 NB> Bringing the thread from the Golded echo about Jamnntpd over here. Here's
a
 NB> test to see if those characters are before level 2 and 3 quotes on this
 NB> reply.

They are there on 2 and 3 (now 3 and 4) level quotes.


Bye, Wilfred.

--- FMail-lnx64 2.2.1.1
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 15/0 90/1 103/705 105/81 106/201 124/5016 128/260 135/225
SEEN-BY: 153/757 7715 154/10 30 203/0 218/700 221/0 226/30 227/114
SEEN-BY: 229/110 112 113 206 307 317 426 428 470 664 700 240/1120
SEEN-BY: 240/5832 266/512 280/464 5003 5555 282/1038 291/111 292/8125
SEEN-BY: 301/1 310/31 320/219 322/757 341/66 234 342/200 396/45 423/120
SEEN-BY: 460/58 256 1124 467/888 633/280 712/848 770/1 5020/400 5054/30
PATH: 280/464 460/58 229/426