Subj : JamNNTPd and UTF-8
To   : Carlos Navarro
From : Nicholas Boel
Date : Sun Feb 25 2024 09:45:40

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)

.