----------------------------------------------------------------------------------
@MSGID: 1:154/10 6621b7c0
@REPLY: 1:153/757.21@fidonet 1388c142
@PID: SmapiNNTPd/Linux 2.4.1
@CHRS: UTF-8 4
@TZUTC: -0500
@TID: hpt/lnx 1.9 2024-02-05
Hello August,
On Fri, 19 Apr 2024 00:32:00 -0400, you wrote:
AA> Well.. the code for OpenXP is open-source. If you know Pascal,
AA> go for it! :D
No, it`s ok.
AA> It stays UTF-8 going out when replying to UTF-8 messages that
AA> had arrived via nntp. It just not work that way with FTN
AA> messages.
Oh, you mean it uses a UTF-8 CHRS kludge? Or do you mean the
UTF-8 text is unchanged when you reply to it, even though it displays
all question marks for the text?
AA> Well.. maybe OpenXP`s UTF-8 support is a minimal subset. For
AA> true unadulterated UTF-8 reading and replying, I use Sylpheed
AA> for specific echoes.
I have a few newsreaders here that I`ve been tinkering with also. ;)
AA> I have plenty of examples that render full width in my current
AA> configuration:
AA> https://ibb.co/y0pypJk
AA> Even yours..
AA> https://ibb.co/bdxGz5t
Are you using the Linux version? I only ask because your tearline
doesn`t have anything to do with `Win`, or `Win32`, or `Windows` like mine
did.
I wonder if I set this up on Linux with the exact same settings
if things might be a bit different.
Regards,
Nick
... Take my advice, I don`t use it anyway.
--- Mozilla Thunderbird
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
SEEN-BY: 50/109 104/117 120/616 123/10 129/215
153/757 154/10 30 40 50 700
SEEN-BY: 218/840 220/90 221/1 6 360 226/1701
280/464 5555 301/1 335/364
SEEN-BY: 341/66 234 460/58 463/68 467/888 2320/105
3634/12 5000/111 5001/100
SEEN-BY: 5005/49 5015/46 5019/40 5020/715 846 848
1042 4441 12000 5030/49
SEEN-BY: 5030/1081 5054/8 5058/104 5060/900 5061/133
5075/128 5083/444
@PATH: 154/10 221/6 5020/1042 4441