Hi,
On 2015-10-02 16:11:36, Maurice Kinal wrote to Wilfred van Velzen:
about: "Re: strftime list":
WvV>> Anyway there seems to be something wrong with your UTC time!
MK> Not when it leaves here. Somewhere it is getting corrupted. For the
MK> record this reply shows "02 Oct 15 17:11:36" in the header. It will be
MK> different on every BBS I have seen my posts/replies posted in as they seem
MK> to want to convert it to whatever they think it should be rather than what
MK> it actually is. Check the raw pkt to see if that is the case please.
The time in the raw pkt was indeed 17:11:36. So it must be a local problem on
my system. I'll investigate!
What is the header time of this message when it arrives on yours? It should be
22:16:36 ...
MK> Also "02 Oct 15 17:11:36" is exactly 2 hours different than "vrijdag,
MK> 02 oktober 2015, 19:11:36 +0200" which is what I am sending in the
MK> packed msg. If you see different than it seems to me that my
MK> additional nonFTN datetime stamp (between the -={ and }=- characters)
MK> is indeed superior to the packed msg header
Your datetime stamp is only suitable for the human readers of your messages.
Processing software can do nothing with it.
MK> which is more ammunition in my favour when I claim that the FTSC is
MK> corrupting data. The only way I could improve it is to change it to
MK> RFC-3339 format.
The FTSC is doing nothing to data traveling in fidonet. It's documenting
current practice. If you want some current fidonet standard changed, you should
talk to all the developers of fidonet software, and convince all fidonet
participants to only use currently maintained software. Good luck with that! ;)
WvV>> 'TZUTC: 0000' kludge
MK> Errrr ... TZUTC: +0000 would be correct. 0000 is corruption by definition
MK> since it lacks the + character as per real world standards for utc
offsets.
MK> Anyone who says different should be taken out back to the woodshed for
MK> applied corrective measures. :::evil grin:::
Is your middle name maybe Don Quichotte? ;)
Bye, Wilfred.
--- FMail-W32-1.69.8.137-B20151001
* Origin: Native IPv6 connectable node (2:280/464)
|