Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2086  |
|  Tommi Koivula to Oli  |
|  Testing smartquote  |
|  19 Oct 19 08:17:48  |
 MSGID: 2:221/0 5daa9c74 REPLY: 2:280/464.47 5da9c538 PID: SmapiNNTPd/Linux-Pi/IPv6 1.3 20191018 EID: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) CHRS: IBMPC 2 TZUTC: 0300 TID: hpt/lnx 1.9.0-cur 2019-09-09 Oli - Tommi Koivula <47@464.280.2> wrote: OTK> On 18.10.19 14:00, Tommi Koivula -> Wilfred van Velzen wrote: OTK> TK> On 18.10.2019 11:39, Wilfred van Velzen wrote: OTK> OTK> ˙˙TK>>>>>> "smartquote" seems to work fine only with "def_showto off" Ok, It is not the problem with smartquote, it is a "feature" of "def_showto on" and how newsclient uses the From: field. As you can see, this news client thinks your initials are OTK. OTK> TK> Ok.. I believe it is not a good idea to let jamnntpd modify utf-8 OTK> messages after posting. Or any messages. :) OTK> OTK> I never saw these UTF-8 characters in the GoldEd or Thunderbird before, OTK> but I see them in Thunderbird's source view now. I wonder why nobody OTK> complained before. I hope it can be fixed easily, I really like the OTK> smartquote option. If you cannot see the incorrect utf-8 characters, it is hard to complain. ;) OTK> TK> X-JAM-PID: SmapiNNTPd/Linux-Pi/IPv6 1.3 20191018 OTK> OTK> Where can I get that version? You cant. Well, at least not yet. It is my test version based on smapinntpd 1.1, with known jamnntpd bugs hopefully fixed. 'Tommi --- * Origin: nntp://rpi.rbb.bbs.fi (2:221/0) SEEN-BY: 1/123 15/2 154/10 203/0 221/1 6 242 360 227/114 229/354 426 SEEN-BY: 229/452 1014 240/1120 5832 249/206 317 280/464 5003 5555 SEEN-BY: 310/31 317/3 322/757 342/200 423/81 PATH: 221/1 280/464 229/426 |
[ << oldest | < older | list | newer > | newest >> ]