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 65d869ee
REPLY: 1:154/10 65d7dc25
Hi Nicholas,

On 2024-02-22 17:42:10, you wrote to you:

  CN>>>>> I've found that this issue can be fixed by adding
  CN>>>>> "-keepsoftcr" to the corresponding line in jamnntpd.xlat,
  CN>>>>> just like with CP866:

  CN>>>>> ================================
  CN>>>>> read UTF-8   utf-8   -keepsoftcr
  CN>>>>> ================================

  BP>>>> problem with jamnntpd is that it does not support multibyte,
  BP>>>> so only can change singlebyte in diffrent charsets

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

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

 NB> Quoted the whole thing in Golded. I don't see anything here. I also hex
 NB> dumped the message before replying to it, and didn't see anything in there
 NB> either. *shrug*

They are in your message! And I see them:

0160   74 2C 0D 20  C2 A0 43 4E  3E 3E 3E 3E  20 6A 75 73  t,.  CN>>>> jus
                    ^^ ^^


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