Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2403  |
|  Tommi Koivula to Tommi Koivula  |
|  Re: JamNNTPd and UTF-8  |
|  01 Mar 24 08:57:22  |
 MSGID: 2:221/1.0 65e17c50 REPLY: 2:221/1.0 65e17af2 PID: JamNNTPd/Linux/IPv6 m32 mxo 20240301 NOTE: HotdogEd/2.13.5 (Android; Google Android; rv:1) Hotdoged/1706655315000 HotdogEd/2.13.5. CHRS: UTF-8 4 TZUTC: 0200 TID: hpt/lnx 1.9 2024-02-05 Hello, Tommi Koivula. On 01/03/2024 8.51 you wrote: TK> On 25.02.2024 13:25, Carlos Navarro wrote: ??>> BP> problem with jamnntpd is that it does not support multibyte, ??>> You're right about JamNNTPd not supporting multibyte. It wraps lines ??>> at 79 bytes, not at 79 chars. Therefore those that have UTF-8 chars ??>> (2 or more bytes) become shorter when wrapped. The more UTF-8 chars a ??>> line has, the shorter. TK> Actually by default Jamnntpd wraps to 72, not 79, but that is irrelevant. :) As you said, the problem with utf-8 text is that Jamnntpd counts bytes, not chars. TK> I've set "#define WRAP_WIDTH 972" now in this Jamnntpd. I can re-wrap quoted text with Ctrl-R in TB. Seems nice so far. TK> 'Tommi TK> ...0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 TK> 'Tommi http://pics.rsh.ru/img/Screens5769_saapazgl.jpg Looks ok now in Hotdoged. --- * Origin: jamnntpd/lnx (2:221/1.0) 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/1 6 242 360 226/30 SEEN-BY: 227/114 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/81 SEEN-BY: 423/120 460/58 256 1124 467/888 633/280 712/848 770/1 5020/400 SEEN-BY: 5054/30 PATH: 221/1 280/464 460/58 229/426 |
[ << oldest | < older | list | newer > | newest >> ]