TIP: Click on subject to list as thread! ANSI
echo: ftsc_public
to: MAURICE KINAL
from: KEES VAN EETEN
date: 2014-10-15 20:29:00
subject: FTSC-5001 question

Hello Maurice!

15 Oct 14 15:20, you wrote to me:

 MK> However in the name of "pot stirring" I see another opportunity to call
 MK> into question the credibility of the fts-4008.002 with respect to real
 MK> world standards (see time.h regarding proper timezone usage).

 I agree in Linux I follow the posix standard end whatever rules there,
 in fidonet I follow fidonet standards. Just as with message formats,
 Fidonet does not comply with RFC822 either. You need a conversion there,
 the same count for the time notation.

 MK> Speaking of ghosts, I note you are still deploying the corrupted TZUTC
 MK> kludge -> TZUTC: 0200.  Das ist vorboten.  It is supposed to be -> TZUTC:
 MK> +0200 as per real world specs as evidenced by any time.h that I have EVER
 MK> run across.  Whoever is responsible for fts-4008.002 should be taken out
 MK> back to the woodshed methinks before that particular document is either
 MK> eradicated or (preferrably) corrected.  Given proper deployment it could
 MK> have been a good fix for the obsolete DateTime stamp the DOS ghosts seem
 MK> to be enamoured with ... which is what appears to have contributed to
 MK> their demise in the first place.

 You attribute a lot to "+" sign that is redundant in most notations anyway.

Kees

--- FPD v2.9.040207  GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.