• TZUTC

    From Deon George@3:633/509 to All on Wednesday, May 20, 2020 22:38:03
    Howdy,

    I'm posting some messages with txt2pkt - but the messages are missing the TZUTC
    kludge. Setting the var TZUTC didnt do anything.

    Is there a variable to tell txt2pkt the current timezone, so that messages posted have the right timestamp?

    ...лоеп

    ... Typographers rule, OQ
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)
  • From Michael Dukelsky@2:5020/1042 to Deon George on Wednesday, May 20, 2020 17:16:42
    Hello Deon,

    Wednesday May 20 2020, Deon George wrote to All:

    I'm posting some messages with txt2pkt - but the messages are missing
    the TZUTC kludge. Setting the var TZUTC didnt do anything.

    Is there a variable to tell txt2pkt the current timezone, so that
    messages posted have the right timestamp?

    AFAIK no.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Moscow, Russia (2:5020/1042)
  • From Deon George@3:633/509 to Michael Dukelsky on Thursday, May 21, 2020 08:15:32
    Re: TZUTC
    By: Michael Dukelsky to Deon George on Wed May 20 2020 05:16 pm

    AFAIK no.

    :(

    I did work out, if I set TZ=0000 before calling txt2pkt, the packet was atleast
    rendered with UTC time - and thus was the correct time (although being in UTC)...

    It would be great if it could detect and use /etc/timezone or /etc/localtime and set the TZ kludge appropriately...

    ...лоеп

    ... Under capitalism man exploits man; under socialism the reverse is true.
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)
  • From Tommi Koivula@2:221/1 to Deon George on Thursday, May 21, 2020 08:24:22
    Hi Deon.

    21 May 20 08:15:32, you wrote to Michael Dukelsky:

    Re: TZUTC
    By: Michael Dukelsky to Deon George on Wed May 20 2020 05:16 pm

    AFAIK no.

    :(

    I did work out, if I set TZ=0000 before calling txt2pkt, the packet
    was atleast rendered with UTC time - and thus was the correct time (although being in UTC)...

    It would be great if it could detect and use /etc/timezone or /etc/localtime and set the TZ kludge appropriately...

    You can put any kludges into the text file to be posted.

    Like this:

    === Cut ===
    echo %@char[1]CHRS: CP437 2 >tmpfile
    echo %@char[1]X-OOPS: :-D >>tmpfile
    echo %@char[1]TZUTC: 0300 >>tmpfile
    uptime >>tmpfile
    txt2pkt.exe -e rbb.test -d \bbs\inbound\local -xf 2:221/1 -xt 2:221/1 tmpfile hpt toss
    === Cut ===

    'Tommi

    ---
    * Origin: - rbb.fidonet.fi - Finland - (2:221/1)
  • From Deon George@3:633/509 to Tommi Koivula on Thursday, May 21, 2020 16:00:31
    Re: TZUTC
    By: Tommi Koivula to Deon George on Thu May 21 2020 08:24 am

    You can put any kludges into the text file to be posted.

    Thanks Tommi, I'll give it a go <thumbs up>

    ...лоеп

    ... I do not often attack the labour party. They do it so well themselves.
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)
  • From Deon George@3:633/509 to Tommi Koivula on Thursday, May 21, 2020 16:28:58
    Re: TZUTC
    By: Deon George to Tommi Koivula on Thu May 21 2020 04:00 pm

    So this worked a treat, thank you.

    It gave me an idea, since I was piping from stdin to txt2pkt, I created another
    script with just:

    (echo -e \\x01CHRS: CP437 2 && echo -e \\x01TZUTC: 1000 && cat)

    That worked just as well.

    Now, it would be great if "hpt" and "htick" recognised or added a TZUTC to messages. eg: If I do "hpt afix <node> %LIST" the resulting netmail sent to <node> has the wrong time... Any tips for this use case?

    ...лоеп

    ... I can't promise anything but I can promise 100%.
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)
  • From Michael Dukelsky@2:5020/1042 to Deon George on Thursday, May 21, 2020 10:36:38
    Hello Deon,

    Thursday May 21 2020, Deon George wrote to Michael Dukelsky:

    It would be great if it could detect and use /etc/timezone or /etc/localtime and set the TZ kludge appropriately...

    I've already put it in my to do list, but the list is rather long, so I don't know when the turn will reach this task. It would be nice if anyone had done this before.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Moscow, Russia (2:5020/1042)
  • From mark lewis@1:3634/12 to Tommi Koivula on Thursday, May 21, 2020 06:36:54
    Re: TZUTC
    By: Tommi Koivula to Deon George on Thu May 21 2020 08:24:22


    === Cut ===
    echo %@char[1]CHRS: CP437 2 >tmpfile
    echo %@char[1]X-OOPS: :-D >>tmpfile
    echo %@char[1]TZUTC: 0300 >>tmpfile

    4DOS/4OS2 is really nice, isn't it ;)


    )\/(ark
    --- SBBSecho 3.11-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From mark lewis@1:3634/12 to Deon George on Thursday, May 21, 2020 06:39:40
    Re: TZUTC
    By: Deon George to Tommi Koivula on Thu May 21 2020 16:28:58


    Now, it would be great if "hpt" and "htick" recognised or added a
    TZUTC to messages. eg: If I do "hpt afix <node> %LIST" the resulting netmail sent to <node> has the wrong time...

    please define "wrong time"... if you run the command at noon your local time, what time stamp is in the message generated? what is your offset from UTC? what
    time stamp do you expect to see?


    )\/(ark
    --- SBBSecho 3.11-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From Tommi Koivula@2:221/0 to mark lewis on Thursday, May 21, 2020 14:11:20
    Hello, mark lewis.
    On 21/05/2020 6.36 you wrote:

    Re: TZUTC
    By: Tommi Koivula to Deon George on Thu May 21 2020 08:24:22
    === Cut ===
    echo %@char[1]CHRS: CP437 2 >tmpfile
    echo %@char[1]X-OOPS: :-D >>tmpfile
    echo %@char[1]TZUTC: 0300 >>tmpfile
    4DOS/4OS2 is really nice, isn't it ;)

    As well as 4nt/tcc. ;)

    )\/(ark

    --
    Tommi

    ---
    * Origin: rbb.fidonet.fi (2:221/0)
  • From Deon George@3:633/509 to mark lewis on Thursday, May 21, 2020 23:07:34
    Re: TZUTC
    By: mark lewis to Deon George on Thu May 21 2020 06:39 am

    please define "wrong time"... if you run the command at noon your local time, what time stamp is in the message generated? what is your offset from UTC? what time stamp do you expect to see?

    Well, "wrong time" is probably not correct.

    The packet gets created with the "current time" without any TZUTC - so when it gets imported into Synchronet, its recorded as "the time" "UTC" - which for me is 10 hrs into the future.

    If it had the TZUTC kludge of 1000, indicating that "the time" is 10hrs ahead of GMT, it would be the "correct time".

    The same would be true, if the packet was (instantly) sent to London and imported, it would still show as 10hrs in the future.

    ...лоеп

    ... Winning isn't the end of the world.
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)
  • From mark lewis@1:3634/12 to Deon George on Thursday, May 21, 2020 09:35:23
    Re: TZUTC
    By: Deon George to mark lewis on Thu May 21 2020 23:07:34


    please define "wrong time"... if you run the command at noon your
    local time, what time stamp is in the message generated? what is
    your offset from UTC? what time stamp do you expect to see?

    The packet gets created with the "current time" without any TZUTC -
    so when it gets imported into Synchronet, its recorded as "the time"
    "UTC" - which for me is 10 hrs into the future.

    gotcha! i thought that's what you were talking about...

    this is a case of damned if you do and damned if you don't... sbbsecho could import and assume local time for messages without a TZUTC control line which would be correct in the case of same TZ posts but wrong for all others... it is
    a problem with only one solution... the trick is to get all software to export messages with the proper TZUTC control line... this can be done for currently maintained software but not older abandoned software...

    if fidonet technology were to be designed today, with the knowledge we have and
    the prospect of international messaging, a lot of the little niggly problems like this would be taken into account and handled properly... unfortunately fidonet technology started as a small block and other blocks were added as we went along to handle specific cases as they cropped up...


    )\/(ark
    --- SBBSecho 3.11-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From Tommi Koivula@2:221/1 to Deon George on Thursday, May 21, 2020 18:20:24

    21 May 20 16:28, Deon George wrote to Tommi Koivula:

    Re: TZUTC
    By: Deon George to Tommi Koivula on Thu May 21 2020 04:00 pm

    So this worked a treat, thank you.

    It gave me an idea, since I was piping from stdin to txt2pkt, I created
    another
    script with just:

    (echo -e \\x01CHRS: CP437 2 && echo -e \\x01TZUTC: 1000 && cat)

    That worked just as well.

    Great! I may use that in my linux system. :)

    'Tommi

    ---
    * Origin: rbb.fidonet.fi (2:221/1)