Subj : JamNNTPd and UTF-8
To   : Nicholas Boel
From : Nicholas Boel
Date : Thu Feb 22 2024 17:42:10

Hello Accession,

On Thursday February 22 2024 17:40, I wrote to Carlos Navarro:

 NB> On Tue, 20 Feb 2024 23:56:32 +0100, Carlos Navarro -> Benny Pedersen
 NB> wrote:

 CN>> 08/02/2024 6:08, Benny Pedersen -> Carlos Navarro:

  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.

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

Regards,
Nick

.... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20231004
 * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

.