@CHRS: IBMPC 2
X-XP-NTP: 30
X-XP-Charset: IBM437
F-TO: Michiel van der Vlist
LEN: 2589
My original message had IBM437.
But, it arrived bearing an IBMPC kludge on the local NNTP side. :(
So, it appears that it left the bossnode with the IBMPC kludge as
well. :(
But, it arrived bearing an IBMPC kludge on the local NNTP side. :(
So, it appears that it left the bossnode with the IBMPC kludge as
well. :(
@MSGID: 3:640/1384.125 5edf3618^
@REPLY: 2:280/5555 5edf2b10
@PID: JamNNTPd/Linux 1
@CHRS: UTF-8 2
Not all. Just the one in question, for the present.
@CHRS: UTF-8 2^
Not all. Just the one in question, for the present.
JamNNTP has bugs as well in delaing with UTF-8. See above. Also,
AFAIK, it assumes that the header is always Latin-1.
Hello Paul,
On Tuesday June 09 2020 17:11, you wrote to me:
@MSGID: 3:640/1384.125 5edf3618^
@REPLY: 2:280/5555 5edf2b10
@PID: JamNNTPd/Linux 1
@CHRS: UTF-8 2
@CHRS: UTF-8 2
^
JamNNTP has bugs as well in delaing with UTF-8. See above. Also,
AFAIK, it assumes that the header is always Latin-1.
Yes. Perfection is difficult with Fidonet; it's an amateur
undertaking.
That JamNNTPd is in a UTF-8 Linux environment and has been told not to make any translations. That Thunderbird is in the /same/ environment.
And now?@PID: JamNNTPd/Linux 1^
@CHRS: UTF-8 2
The "UTF-8 2" instead of "UTF8-8 4" isn't really a problem I think.
AFAIK all readers/editor that can do UTF-8 seem to ignore the level
field. I have not heard of a counter example yet.
That JamNNTPd is in a UTF-8 Linux environmentThat it insists the header is always Latin-1 independant of the
encoding of the text body is what I consider am more sreious problem.
@CHRS: UTF-8 2
And now?
As I understand it, it's trying to deal with stuff not in the 'text'
body. Is that close? :)
X-XP-Charset: IBM437
My original message had IBM437.
But, it arrived bearing an IBMPC kludge on the local NNTP side. :(
So, it appears that it left the bossnode with the IBMPC kludge as
well. :(
My original message had IBM437.
Hmmm.. Then FTSC should update their documentation of common terms
and practices out in the real world. LOL
https://www.compart.com/en/unicode/charsets/IBM437
https://www.iana.org/assignments/character-sets/character-sets.xhtml
But, it arrived bearing an IBMPC kludge on the local NNTP side.
:(
So, it appears that it left the bossnode with the IBMPC kludge
as well. :(
Yes.. something a little strange is happening there! LOL
EMP: /FIDO/FIDOTEST
ABS: August Abolins@2:221/1.58
BET: Test From Blue Wave Door
EDA: 20200607184000S-4
MID: 2:221/1.58@fidonet e533a982
BEZ: 2:221/1.58@fidonet e533a612
BEZ: 2:280/5555 5edd28c5
ROT:
MAILER: OpenXP/5.0.44 (Win32)
ORG: /|ug's Point
X_C:
X-XP-NTP: 30
X-XP-Charset: IBM437
F-TO: Michiel van der Vlist
LEN: 2589
My original message had IBM437.
But, it arrived bearing an IBMPC kludge on the local NNTP side. :(:(
So, it appears that it left the bossnode with the IBMPC kludge as well.
Thoughts, Tommi?
That's exactly the CHRS kludge in your message with MSGID "e533a982".
Stop using OpenXP if you want to study kludges.
@MSGID: 2:221/1.0 5edf676e
@REPLY: 2:280/5555 5edf44a6
@PID: JamNNTPd/OS2 1.3 20200606
@CHRS: UTF-8 4
@TZUTC: 0300
@TID: FastEcho 1.46.1 1530
On 9.6.2020 11.13, Michiel van der Vlist : Paul Quinn wrote:
Hello Paul,
On Tuesday June 09 2020 17:11, you wrote to me:
@MSGID: 3:640/1384.125 5edf3618^
@REPLY: 2:280/5555 5edf2b10
@PID: JamNNTPd/Linux 1
@CHRS: UTF-8 2
And now?
'Tommi
SEEN-BY: 103/705 154/10 203/0 221/1 6 360 229/101 240/1120 5832
280/464
SEEN-BY: 280/5003 5555 288/100 292/8125 310/31 396/45 423/81 120
712/848
SEEN-BY: 770/1 2452/250
@PATH: 221/1 280/464
https://www.compart.com/en/unicode/charsets/IBM437
https://www.iana.org/assignments/character-sets/character-sets.xhtml
If CP437 is (which is an alias, btw), then IBM437 (the proper name)
is.
Granted, I heard that oxp was adapted for ftn, but it works quite well afaik.
If you have a grievance, take it up with the developer with your officiality and tell him how broken oxp is.
But, it arrived bearing an IBMPC kludge on the local NNTP side. :(
MvdV> So it would seem that entering messages via an NNTP gateway is
MvdV> buggy...
Not all. Just the one in question, for the present.
For August... which one please, mate?
Stop using OpenXP if you want to study kludges.
For August... which one please, mate?
The problem has been identified in the code. There is a deliberate
change of ibm437 to ibmpc before packing. There is no buggyness.
The only buggyness is the rapid jumping to conclusions and the final solutions by select few people.
Sheesh.
Hello Tommi!
** On Tuesday 09.06.20 - 17:31, Tommi Koivula wrote to August Abolins:
Stop using OpenXP if you want to study kludges.
ROTFL. (Oooops, now I need help to get up!)
Granted, I heard that oxp was adapted for ftn, but it works quite well
afaik.
Thoughts, Tommi?
Stop using OpenXP if you want to study kludges.
Hello Tommi!
*** Tuesday 09.06.20 at 17:31, Tommi Koivula wrote to August Abolins: [snip]
Thoughts, Tommi?
Stop using OpenXP if you want to study kludges.Perhaps you meant don't use OpenXP to study kludges.
Regards,
Martin
MvdV> It seems it was written for e-mail and usenet mail and FTN was
MvdV> added as an afterthought.
"CrossPoint v1.0 was released in 1992 as shareware for the DOS operating system. It was a pure point program for Z-Netz and its data exchange protocol Netcall. Version 2.0 appeared at the end of 1992, which also supported FidoNet, MausNet, MagicNet, QuickMail and the data format of
the new Z-Netz protocol ZConnect."
Hardly an afterthought, more of a development of the software, IMO.
If you have a grievance, take it up with the developer with your
officiality and tell him how broken oxp is.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 368 |
Nodes: | 16 (2 / 14) |
Uptime: | 52:35:23 |
Calls: | 7,887 |
Calls today: | 1 |
Files: | 12,962 |
Messages: | 5,788,718 |