TZUTC: 1100   
   MSGID: 50262.dove-syncdisc@12:1/2 2bce6cc4   
   REPLY: 53307.sync@1:103/705 2bcd4cc2   
   PID: Synchronet 3.20a-Linux master/7b932f63e Dec  9 2023 GCC 10.2.1   
   TID: SBBSecho 3.23-Linux master/f9ad15e85 Dec 21 2024 GCC 12.2.0   
   COLS: 80   
   BBSID: ALTERANT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: JS Object save_msg()   
     By: Digital Man to deon on Sat Dec 21 2024 02:51 pm   
      
   Howdy,   
      
    > No, it would not. The mktime() standard C library function uses *your* local   
    > time zone (not mine) in the conversion to time_t. There isn't a standard C   
    > runtime library function that takes a broken-down date/time and converts it   
    > to a time_t using an arbitrary (user supplied) time zone. The rest of your   
    > message seemed dependant on this first incorrect assumption.   
      
   Oh, that was a bad assumption on my part. I did think when_import_time was a   
   valid time_t value. (IE: The utc time the message was written.)   
      
   I wanted to check it out, so I set up my test system to UTC-8:00, and exported   
   a messages to FTN to clrghouz, then into Alterant (UTC+11:00), and indeed, on   
   my test system:   
      
   when_written     6764CEAC FE20 Thu Dec 19 17:55:56 2024 UTC-8:00   
      
   Is a valid time_t for the printed time, and on alterant   
      
   when_written     6763C37C FE20 Thu Dec 19 17:55:56 2024 UTC-8:00   
      
   it is not.   
      
   Incidently, the time_t on alterant 1734591356, is exactly 19hrs incorrect,   
   which just so happens to be the difference in our timezones.   
      
      
   ...ëîåï   
      
   ---   
    þ Synchronet þ AnsiTEX bringing back videotex but with ANSI   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 203/0 218/700 221/0 226/30 227/114 229/110 114 206   
   SEEN-BY: 229/317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 282/1038 291/111 292/8125 301/1 310/31   
   SEEN-BY: 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58   
   SEEN-BY: 467/888 633/267 280 281 384 410 418 420 2744 712/848 770/1   
   SEEN-BY: 902/26 5020/400 5075/35   
   PATH: 103/705 280/464 633/280 229/426